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   [EMAIL PROTECTED]   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
  [EMAIL PROTECTED]               |  (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>

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Reply via email to