Re: [SQL] Error calling self-made plpgsql function "function XYZ(bigint) does not exist"

Jep... but pgAdmin_III inserts dbl-quotes, if there is some CamelCase... but from sql-console i can create objects w/ or w/o dbl-quotes, but in result i always get lower-cased objects.. Seems, i should `recreate` my db in lowercase.. it will take some time :( Thanks for advance. PS: problem he

Re: [SQL] Error calling self-made plpgsql function "function XYZ(bigint) does not exist"

On Jan 20, 2006, at 1:45 , Leif B. Kristensen wrote: That is usual behaviour for RDBMSes. They are case-insensitive if you use ALL_CAPS or small_letters only. PostgreSQL is case-insensitive in the sense that it down-cases identifiers that are not double-quoted, e.g., MYSUPERFIELD -> mysup

Re: [SQL] indexing for left join

Rod Taylor wrote: Sequential despite the indices? Or is this because the tables of my test DB are virtually empty? This is it. PostgreSQL changes strategies with data load. Performance testing must be done on an approximation of the real data (both values and size). Thanks for your responses

Re: [SQL] indexing for left join

Milorad Poluga wrote: Try to execute this modification of your query : SELECT ITEM.ITEM_PK FROM ITEM LEFT JOIN SERIAL_NO ON ( SERIAL_NO.ITEM_FK = ITEM.ITEM_PK AND SERIAL_NO.NO ='WX1234' ) GROUP BY ITEM.ITEM_PK SELECT ITEM.ITEM_PK FROM ITEM LEFT JOIN SERIAL_NO O

Re: [SQL] Error calling self-made plpgsql function "function XYZ(bigint) does not exist"

On Thursday 19 January 2006 14:06, Juris wrote: >Argh... big thanks.. did not know what pgAdmin/PG have any >case-sensitive issues with functions... > >Also for fields it is relative... without dbl-quotes i could not query >anything (i am using "MySuperField"-like field names) That is usual behavi

Re: [SQL] indexing for left join

T E Schmitz wrote: Sequential despite the indices? Or is this because the tables of my test DB are virtually empty? Yes - read up on analyse and column statistics for details. Oh, you've probably missed about vacuuming too. -- Richard Huxton Archonet Ltd ---(en

Re: [SQL] indexing for left join

> Sequential despite the indices? Or is this because the tables of my test > DB are virtually empty? This is it. PostgreSQL changes strategies with data load. Performance testing must be done on an approximation of the real data (both values and size). -- ---(end of br

[SQL] indexing for left join

I have two tables: TABLE ITEM ( ITEM_PK serial, RETAIL_PRICE numeric (7,2) NOT NULL, ... PRIMARY KEY (ITEM_PK) ) TABLE SERIAL_NO ( SERIAL_NO_PK serial, NO varchar (20) NOT NULL, NAME varchar (20), ITEM_FK integer NOT NULL, PRIMARY KEY (SERIAL_NO_PK) ); common query: SELECT ITEM.ITEM_PK FROM IT

Re: [SQL] Error calling self-made plpgsql function "function XYZ(bigint) does not exist"

Argh... big thanks.. did not know what pgAdmin/PG have any case-sensitive issues with functions... Also for fields it is relative... without dbl-quotes i could not query anything (i am using "MySuperField"-like field names) 2006/1/19, Michael Glaesemann <[EMAIL PROTECTED]>: > > On Jan 19, 2006, a

Re: [SQL] Error calling self-made plpgsql function "function XYZ(bigint) does not exist"

On Jan 19, 2006, at 21:39 , Juris wrote: == sql begin == CREATE OR REPLACE FUNCTION "InventGroups_GetAllParents"(int8) select * from InventGroups_GetAllParents(0::int8) === ERROR: function inventgroups_getallparents(bigint) does not exist HINT: No function matches the given name and ar

[SQL] Error calling self-made plpgsql function "function XYZ(bigint) does not exist"

Hi I have problem calling my function (prety easy): == sql begin == CREATE OR REPLACE FUNCTION "InventGroups_GetAllParents"(int8) RETURNS SETOF "ItemGroupRelationNode" AS $BODY$declare R RECORD; SR RECORD; begin FOR R IN select ItemGroupId, ParentItemGroupId