Re: SQLCODE==-209 - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: SQLCODE==-209
Date
Msg-id 200110112025.f9BKPRW09083@candle.pha.pa.us
Whole thread Raw
In response to Re: SQLCODE==-209  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: SQLCODE==-209  (John Summerfield <pgtest@os2.ami.com.au>)
List pgsql-bugs
I have added documentation for code 209.  Looks like there are other
undocumented ones.  Should we document them all?

> John Summerfield writes:
>
> > I'm using 7.2devel from CVS, and as I've already reported, the documentation doesn't build.
>
> http://www.ca.postgresql.org/devel-corner/docs/postgres/index.html
>
> > Consequently I'm forced to rely on documentation for 7.1.2/3 which
> > does not mention -209, at least in the ecpg documentation I'm looking
> > at,
>
> 7.2 doesn't document it either...
>
> --
> Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
Index: doc/src/sgml/ecpg.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v
retrieving revision 1.23
diff -c -r1.23 ecpg.sgml
*** doc/src/sgml/ecpg.sgml    2001/09/13 15:55:22    1.23
--- doc/src/sgml/ecpg.sgml    2001/10/11 20:04:49
***************
*** 332,337 ****
--- 332,347 ----
        </varlistentry>

        <varlistentry>
+        <term><computeroutput>-209, NULL value without indicator in line %d.</computeroutput></term>
+        <listitem>
+     <para>
+      <productname>Postgres</productname> returned <symbol>ECPG_MISSING_INDICATOR</symbol>
+      because a NULL was returned and no NULL indicator variable was supplied.
+     </para>
+        </listitem>
+       </varlistentry>
+
+       <varlistentry>
         <term><computeroutput>-220, No such connection %s in line %d.</computeroutput></term>
         <listitem>
      <para>

pgsql-bugs by date:

Previous
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #479: Backend crashes when using certain commands with SJIS encoded databases
Next
From: Bruce Momjian
Date:
Subject: Re: initdb must have write access to /tmp