On Thu, 2 Feb 2006 [EMAIL PROTECTED] wrote:
> The problem was fixed by initializing the array before giving it a
> value. Not surprising Postges isnt as popular as it should be. I was by
> luck that I found this out - the manual says nothing about init arrays.
Well, I think that's in part becaus
[EMAIL PROTECTED] wrote:
The problem was fixed by initializing the array before giving it a
value. Not surprising Postges isnt as popular as it should be. I was by
luck that I found this out - the manual says nothing about init arrays.
Instead of flippant comments like that, submit docs a patch
The problem was fixed by initializing the array before giving it a
value. Not surprising Postges isnt as popular as it should be. I was by
luck that I found this out - the manual says nothing about init arrays.
DECLARE
id_var INTEGER[];
record_var RECORD;
BEGIN
id_var := '{}';
id_var[0] :=
I set the array count to start at 1, but still not working. Im using
v8. Ive also read that the ANY clause runs rediculously slow. Is there
another way to convert an array into a record set without writing a
separate function for that? Is it even possible to create a record set
variable in a functi
[EMAIL PROTECTED] writes:
> Has anyone successfully used the "ANY", "ALL", or "SOME" clause using
> arrays? Cant seem to get this to work. Heres the gist of my function
> which returns a SETOF INTEGER[]...
Works for me, modulo the fact that the code is evidently returning
setof int not setof int[]
[EMAIL PROTECTED] wrote:
Has anyone successfully used the "ANY", "ALL", or "SOME" clause using
arrays? Cant seem to get this to work. Heres the gist of my function
which returns a SETOF INTEGER[]...
DECLARE
id_var INTEGER[];
record_var RECORD;
BEGIN
id_var[0] := 1;
I think by default arr
