From: | John Summerfield <pgtest(at)os2(dot)ami(dot)com(dot)au> |
---|---|
To: | John Summerfield <pgtest(at)os2(dot)ami(dot)com(dot)au> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: SQLCODE==-209 |
Date: | 2001-09-17 18:36:20 |
Message-ID: | Pine.LNX.4.33.0109180230570.5197-100000@dugite.os2.ami.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-patches |
Sorry all. There was a certain amount of nonsence in my previous posting on this topic.
The failing sql command is an fact a select into.
It fails when trying to retrieve a null value. The insert worked (I can retrieve the record
if I don't ask for the null field, so evidently the insert code is correct.
-209 is generated by ecpg.
I still don't know what "indicator" means though.
If I can reasonably be expected to understand the term, there still remains the bug that -209
is undocumented.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2001-09-17 18:37:22 | Re: SQLCODE==-209 |
Previous Message | John Summerfield | 2001-09-17 18:29:09 | Re: Performance and 72.devel |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2001-09-17 18:37:22 | Re: SQLCODE==-209 |
Previous Message | Bruce Momjian | 2001-09-17 15:56:08 | Re: isNullable() |