-<!-- $PostgreSQL: pgsql/doc/src/sgml/ecpg.sgml,v 1.75 2006/09/21 09:10:27 meskes Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/ecpg.sgml,v 1.76 2006/09/22 15:22:04 tgl Exp $ -->
<chapter id="ecpg">
<title><application>ECPG</application> - Embedded <acronym>SQL</acronym> in C</title>
<para>
The following input formats are allowed:
<table>
- <title>Valid input formats for <function>PGTYPESdate_from_asc</function>.
+ <title>Valid input formats for <function>PGTYPESdate_from_asc</function></title>
<tgroup cols="2">
<thead>
<row>
you an idea of how to use this function. All output lines are based on
the same date: November, 23rd, 1959.
<table>
- <title>Valid input formats for <function>PGTYPESdate_fmt_asc</function>.
+ <title>Valid input formats for <function>PGTYPESdate_fmt_asc</function></title>
<tgroup cols="2">
<thead>
<row>
The following table indicates a few possible formats. This will give
you an idea of how to use this function.
<table>
- <title>Valid input formats for <function>rdefmtdate</function>.
+ <title>Valid input formats for <function>rdefmtdate</function></title>
<tgroup cols="2">
<thead>
<row>
<para>
The following table contains a few examples for input strings:
<table>
- <title>Valid input formats for <function>PGTYPEStimestamp_from_asc</function>.
+ <title>Valid input formats for <function>PGTYPEStimestamp_from_asc</function></title>
<tgroup cols="2">
<thead>
<row>
</para>
</listitem>
</varlistentry>
- <variablelist>
<varlistentry>
<term><literal>PGTYPES_DATE_BAD_DATE</literal></term>
</para>
</listitem>
</varlistentry>
- <variablelist>
<varlistentry>
<term><literal>PGTYPES_DATE_ERR_EARGS</literal></term>
</para>
</listitem>
</varlistentry>
- <variablelist>
<varlistentry>
<term><literal>PGTYPES_DATE_ERR_ENOSHORTDATE</literal></term>
</para>
</listitem>
</varlistentry>
- <variablelist>
<varlistentry>
<term><literal>PGTYPES_INTVL_BAD_INTERVAL</literal></term>
</para>
</listitem>
</varlistentry>
- <variablelist>
<varlistentry>
<term><literal>PGTYPES_DATE_ERR_ENOTDMY</literal></term>
</para>
</listitem>
</varlistentry>
- <variablelist>
<varlistentry>
<term><literal>PGTYPES_DATE_BAD_DAY</literal></term>
</para>
</listitem>
</varlistentry>
- <variablelist>
<varlistentry>
<term><literal>PGTYPES_DATE_BAD_MONTH</literal></term>
</para>
</listitem>
</varlistentry>
- <variablelist>
<varlistentry>
<term><literal>PGTYPES_TS_BAD_TIMESTAMP</literal></term>
of ecpg. pgtypeslib maps SQL data types to data types within the C host
program and most of the additional functions of the Informix compatibility
mode allow you to operate on those C host program types. Note however that
- the extend of the compatibility is limited. It does not try to copy Informix
- behaviour but it allows you to do more or less the same operations and gives
+ the extent of the compatibility is limited. It does not try to copy Informix
+ behaviour; it allows you to do more or less the same operations and gives
you functions that have the same name and the same basic behavior but it is
no drop-in replacement if you are using Informix at the moment. Moreover,
some of the data types are different. For example,
- <productname>PostgreSQL's<productname> datetime and interval types do not
+ <productname>PostgreSQL's</productname> datetime and interval types do not
know about ranges like for example <literal>YEAR TO MINUTE</> so you won't
find support in ecpg for that either.
</para>
synonym for ecpg's <literal>DISCONNECT CURRENT</>.
<programlisting>
$CLOSE DATABASE; /* close the current connection */
- EXEC SQL ClOSE DATABASE;
+ EXEC SQL CLOSE DATABASE;
</programlisting>
</para>
</listitem>
</varlistentry>
+ </variablelist>
</para>
</sect2>
</para>
</listitem>
</itemizedlist>
+ </para>
+
<para>
Here is an example of a call to this function:
<programlisting>
</listitem>
</varlistentry>
</variablelist>
+ </para>
<para>
Example: