Pavel Stehule wrote:
>> it's known problem - column and variable names collision, so when you
>> use any SQL statement inside procedure you have to be carefully about
>> using variable names.
Oh, I didn't took notice of that.
Now knowing it is not a bug and how it works, it makes things much easi
2008/6/18 Pavel Stehule <[EMAIL PROTECTED]>:
> Hello
>
> it's known problem - column and variable names collision, so when you
> use any SQL statement inside procedure you have to be carefully about
> using variable names.
>
> postgres=# CREATE OR REPLACE FUNCTION testcur( OUT _a integer, OUT _b in
Hello
it's known problem - column and variable names collision, so when you
use any SQL statement inside procedure you have to be carefully about
using variable names.
postgres=# CREATE OR REPLACE FUNCTION testcur( OUT _a integer, OUT _b integer )
RETURNS SETOF RECORD AS $$
DECLARE
cur ref
Hi!
I did some experiments with cursors and found that my data doesn't get
sorted by the "order by"-statement.
Here is what I did:
CREATE TABLE ta (
a integer NOT NULL,
b integer NOT NULL
);
insert into ta values(3,1);
insert into ta values(1,2);
insert into ta values(4,3
