Skip to content

P
Postgres FD Implementation
Commit cc4f5769 authored by Peter Eisentraut's avatar Peter Eisentraut
Browse files
Options

Improve ECPG documentation.

parent cf8da4e9
Show whitespace changes
Inline Side-by-side
Showing with 1152 additions and 1298 deletions
doc/src/sgml/ecpg.sgml
View file @ cc4f5769
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.37 2002/09/21 18:32:52 petere Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.38 2002/10/21 18:04:05 petere Exp $
-->
<chapter id="ecpg">
<docinfo>
<authorgroup>
<author>
<firstname>Linus</firstname>
<surname>Tolke</surname>
</author>
<author>
<firstname>Michael</firstname>
<surname>Meskes</surname>
</author>
</authorgroup>
<copyright>
<year>1996-1997</year>
<holder>Linus Tolke</holder>
</copyright>
<copyright>
<year>1998</year>
<holder>Michael Meskes</holder>
</copyright>
<date>Transcribed 1998-02-12</date>
</docinfo>
<title><application>ecpg</application> - Embedded <acronym>SQL</acronym>
in <acronym>C</acronym></title>
<chapter id="ecpg">
<title><application>ECPG</application> - Embedded <acronym>SQL</acronym> in C</title>
<indexterm zone="ecpg"><primary>embedded SQL</primary><secondary>in C</secondary></indexterm>
<para>
This describes the embedded <acronym>SQL</acronym> package for
<productname>PostgreSQL</productname>. It works with
This chapter describes the embedded <acronym>SQL</acronym> package
for <productname>PostgreSQL</productname>. It works with
<acronym>C</acronym> and <acronym>C++</acronym>. It was written by
Linus Tolke (<email>linus@epact.se</email>) and Michael Meskes
(<email>meskes@debian.org</email>). The package is installed with the
<productname>PostgreSQL</> distribution, and carries a similar license.
(<email>meskes@postgresql.org</email>).
</para>
<sect1 id="ecpg-why">
<title>Why Embedded <acronym>SQL</acronym>?</title>
<para>
Admittedly, this documentation is quite incomplete. But since this
interface is standardized, additional information can be found in
many resources about SQL.
</para>
<sect1 id="ecpg-concept">
<title>The Concept</title>
<para>
An embedded SQL program consists of code written in an ordinary
programming language, in this case C, mixed with SQL commands in
specially marked sections. To build the program, the source code
is first passed to the embedded SQL preprocessor, which converts it
to an ordinary C program, and afterwards it can be processed by a C
compilation tool chain.
</para>
<para>
Embedded <acronym>SQL</acronym> has advantages over other methods
for handling <acronym>SQL</acronym> queries. It takes care of
the tedious passing of information to and from variables in your
<acronym>C</acronym> or <acronym>C++</acronym> program. Many
<acronym>RDBMS</acronym> packages support this embedded language.
for handling <acronym>SQL</acronym> commands from C code. First, it
takes care of the tedious passing of information to and from
variables in your <acronym>C</acronym> program. Secondly, embedded
SQL in C is defined in the SQL standard and supported by many other
SQL databases. The PostgreSQL implementation is designed to match
this standard as much as possible, and it is usually possible to
port embedded <acronym>SQL</acronym> programs written for other
<acronym>RDBMS</acronym> to <productname>PostgreSQL</productname>
with relative ease.
</para>
<para>
There is an ANSI standard describing how the embedded language
should work. <application>ecpg</application> was designed to match
this standard as much as possible. It is possible to port embedded
<acronym>SQL</acronym> programs written for other
<acronym>RDBMS</acronym> to <productname>PostgreSQL</productname>.
As indicated, programs written for the embedded SQL interface are
normal C programs with special code inserted to perform
database-related actions. This special code always has the form
<programlisting>
EXEC SQL ...;
</programlisting>
These statements syntactically take the place of a C statement.
Depending on the particular statement, they may appear in the
global context or within a function. Embedded SQL statements
follow the case-sensitivity rules of normal SQL code, and not those
of C.
</para>
<para>
The following sections explain all the embedded SQL statements.
</para>
</sect1>
<sect1 id="ecpg-concept">
<title>The Concept</title>
<sect1 id="ecpg-connect">
<title>Connecting to the Database Server</title>
<para>
You write your program in <acronym>C/C++</acronym> with special
<acronym>SQL</acronym> constructs. When declaring variables to be
used in <acronym>SQL</acronym> statements, you need to put them in a
special <command>declare</> section. You use a special syntax for the
<acronym>SQL</acronym> queries.
One connects to a database using the following statement:
<programlisting>
EXEC SQL CONNECT TO <replaceable>target</replaceable> <optional>AS <replaceable>connection-name</replaceable></optional> <optional>USER <replaceable>user-name</replaceable></optional>;
</programlisting>
The <replaceable>target</replaceable> can be specified in the
following ways:
<itemizedlist>
<listitem>
<simpara>
<literal><replaceable>dbname</><optional>@<replaceable>hostname</></optional><optional>:<replaceable>port</></optional></literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal>tcp:postgresql://<replaceable>hostname</><optional>:<replaceable>port</></optional><optional>/<replaceable>dbname</></optional><optional>?<replaceable>options</></optional></literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal>unix:postgresql://<replaceable>hostname</><optional>:<replaceable>port</></optional><optional>/<replaceable>dbname</></optional><optional>?<replaceable>options</></optional></literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal><replaceable>character variable</replaceable></literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal><replaceable>character string</replaceable></literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal>DEFAULT</literal>
</simpara>
</listitem>
</itemizedlist>
</para>
<para>
Before compiling you run the file through the embedded
<acronym>SQL</acronym> <acronym>C</acronym> preprocessor and it
converts the <acronym>SQL</acronym> statements you used to function
calls with the variables used as arguments. Both query input and
result output variables are passed.
There are also different ways to specify the user name:
<itemizedlist>
<listitem>
<simpara>
<literal><replaceable>userid</replaceable></literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal><replaceable>userid</replaceable>/<replaceable>password</replaceable></literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal><replaceable>userid</replaceable> IDENTIFIED BY <replaceable>password</replaceable></literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal><replaceable>userid</replaceable> USING <replaceable>password</replaceable></literal>
</simpara>
</listitem>
</itemizedlist>
The <replaceable>userid</replaceable> and
<replaceable>password</replaceable> may be a constant text, a
character variable, or a character string.
</para>
<para>
After compiling, you must link with a special library that contains
needed functions. These functions fetch information from the
arguments, perform the <acronym>SQL</acronym> query using the
<filename>libpq</filename> interface, and put the result in the
arguments specified for output.
The <replaceable>connection-name</replaceable> is used to handle
multiple connections in one program. It can be omitted if a
program uses only one connection.
</para>
</sect1>
<sect1 id="ecpg-use">
<title>How To Use <application>ecpg</application></title>
<sect1 id="ecpg-disconnect">
<title>Closing a Connection</title>
<para>
This section describes how to use <application>ecpg</application>.
To close a connection, use the following statement:
<programlisting>
EXEC SQL DISCONNECT [<replaceable>connection</replaceable>];
</programlisting>
The <replaceable>connection</replaceable> can be specified
in the following ways:
<itemizedlist>
<listitem>
<simpara>
<literal><replaceable>connection-name</replaceable></literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal>DEFAULT</literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal>CURRENT</literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal>ALL</literal>
</simpara>
</listitem>
</itemizedlist>
</para>
</sect1>
<sect2>
<title>Preprocessor</title>
<sect1 id="ecpg-commands">
<title>Running SQL Commands</title>
<para>
The preprocessor is called <application>ecpg</application>. After
installation it resides in the <productname>PostgreSQL</productname>
<filename>bin/</filename> directory.
Any SQL command can be run from within an embedded SQL application.
Below are some examples of how to do that.
</para>
<para>
Creating a table:
<programlisting>
EXEC SQL CREATE TABLE foo (number integer, ascii char(16));
EXEC SQL CREATE UNIQUE INDEX num1 ON foo(number);
EXEC SQL COMMIT;
</programlisting>
</para>
</sect2>
<sect2>
<title>Library</title>
<para>
The <application>ecpg</application> library is called
<filename>libecpg.a</filename> or <filename>libecpg.so</filename>.
Additionally, the library uses the <filename>libpq</filename>
library for communication to the
<productname>PostgreSQL</productname> server. You will have to link
your program using <parameter>-lecpg -lpq</parameter>.
Inserting rows:
<programlisting>
EXEC SQL INSERT INTO foo (number, ascii) VALUES (9999, 'doodad');
EXEC SQL COMMIT;
</programlisting>
</para>
<para>
The library has some methods that are <quote>hidden</quote> but may prove
useful.
Deleting rows:
<programlisting>
EXEC SQL DELETE FROM foo WHERE number = 9999;
EXEC SQL COMMIT;
</programlisting>
</para>
<itemizedlist>
<listitem>
<para>
<function>ECPGdebug(int <replaceable>on</replaceable>, FILE
*<replaceable>stream</replaceable>)</function> turns on debug
logging if called with the first argument non-zero. Debug
logging is done on <replaceable>stream</replaceable>. Most
<acronym>SQL</acronym> statement log their arguments and results.
Singleton Select:
<programlisting>
EXEC SQL SELECT foo INTO :FooBar FROM table1 WHERE ascii = 'doodad';
</programlisting>
</para>
<para>
The most important function , <function>ECPGdo</function>, logs
all <acronym>SQL</acronym> statements with both the expanded
string, i.e. the string with all the input variables inserted,
and the result from the <productname>PostgreSQL</productname>
server. This can be very useful when searching for errors in
your <acronym>SQL</acronym> statements.
Select using Cursors:
<programlisting>
EXEC SQL DECLARE foo_bar CURSOR FOR
SELECT number, ascii FROM foo
ORDER BY ascii;
EXEC SQL FETCH foo_bar INTO :FooBar, DooDad;
...
EXEC SQL CLOSE foo_bar;
EXEC SQL COMMIT;
</programlisting>
</para>
</listitem>
<listitem>
<para>
<function>ECPGstatus()</function>
This method returns TRUE if we are connected to a database and FALSE if not.
Updates:
<programlisting>
EXEC SQL UPDATE foo
SET ascii = 'foobar'
WHERE number = 9999;
EXEC SQL COMMIT;
</programlisting>
</para>
</listitem>
</itemizedlist>
<para>
The tokens of the form
<literal>:<replaceable>something</replaceable></literal> are
<firstterm>host variables</firstterm>, that is, they refer to
variables in the C program. They are explained in the next
section.
</para>
</sect2>
<sect2>
<title>Error handling</title>
<para>
In the default mode, statements are committed only when
<command>EXEC SQL COMMIT</command> is issued. The embedded SQL
interface also supports autocommit of transactions (as known from
other interfaces) via the <option>-t</option> command-line option
to <command>ecpg</command> (see below) or via the <literal>EXEC SQL
SET AUTOCOMMIT TO ON</literal> statement. In autocommit mode, each
query is automatically committed unless it is inside an explicit
transaction block. This mode can be explicitly turned off using
<literal>EXEC SQL SET AUTOCOMMIT TO OFF</literal>.
</para>
</sect1>
<sect1 id="ecpg-variables">
<title>Passing Data</title>
<para>
To pass data from the program to the database, for example as
parameters in a query, or to pass data from the database back to
the program, the C variables that are intended to contain this data
need to be declared in a specially marked section, so the embedded
SQL preprocessor is made aware of them.
</para>
<para>
This section starts with
<programlisting>
EXEC SQL BEGIN DECLARE SECTION;
</programlisting>
and ends with
<programlisting>
EXEC SQL END DECLARE SECTION;
</programlisting>
Between those lines, there must be normal C variable declarations, such as
<programlisting>
int x;
char foo[16], bar[16];
</programlisting>
</para>
<para>
The declarations are also echoed to the output file as a normal C
variables, so there's no need to declare them again. Variables
that are not intended to be used with SQL commands can be declared
normally outside these special sections.
</para>
<para>
The definition of a structure or union also must be listed inside a
<literal>DECLARE</> section. Otherwise the preprocessor cannot
handle these types since it does not know the definition.
</para>
<para>
The special types <type>VARCHAR</type> and <type>VARCHAR2</type>
are converted into a named <type>struct</> for every variable. A
declaration like:
<programlisting>
VARCHAR var[180];
</programlisting>
is converted into:
<programlisting>
struct varchar_var { int len; char arr[180]; } var;
</programlisting>
This structure is suitable for interfacing with SQL datums of type
<type>VARCHAR</type>.
</para>
<para>
To detect errors from the <productname>PostgreSQL</productname>
server, include a line like:
To use a properly declared C variable in an SQL statement, write
<literal>:<replaceable>varname</></literal> where an expression is
expected. See the previous section for some examples.
</para>
</sect1>
<sect1 id="ecpg-errors">
<title>Error Handling</title>
<para>
The embedded SQL interface provides a simplistic and a complex way
to handle exceptional conditions in a program. The first method
causes a message to printed automatically when a certain condition
occurs. For example:
<programlisting>
exec sql include sqlca;
EXEC SQL WHENEVER sqlerror sqlprint;
</programlisting>
in the include section of your file. This will define a <type>struct</> and
a variable with the name <varname>sqlca</varname> as follows:
or
<programlisting>
EXEC SQL WHENEVER not found sqlprint;
</programlisting>
This error handling remains enabled throughout the entire program.
</para>
<note>
<para>
This is <emphasis>not</emphasis> an exhaustive example of usage
for the <command>EXEC SQL WHENEVER</command> statement. Further
examples of usage may be found in SQL manuals (e.g.,
<citetitle>The LAN TIMES Guide to SQL</> by Groff and Weinberg).
</para>
</note>
<para>
For a more powerful error handling, the embedded SQL interface
provides a <type>struct</> and a variable with the name
<varname>sqlca</varname> as follows:
<programlisting>
struct sqlca
{
......@@ -172,6 +383,7 @@ struct sqlca
char sqlerrmc[70];
} sqlerrm;
char sqlerrp[8];
long sqlerrd[6];
/* 0: empty */
/* 1: OID of processed tuple if applicable */
......@@ -180,6 +392,7 @@ struct sqlca
/* 3: empty */
/* 4: empty */
/* 5: empty */
char sqlwarn[8];
/* 0: set to 'W' if at least one other is 'W' */
/* 1: if 'W' at least one character string */
......@@ -191,22 +404,24 @@ struct sqlca
/* 5: empty */
/* 6: empty */
/* 7: empty */
char sqlext[8];
} sqlca;
</programlisting>
(Many of the empty fields may be used in a future release.)
</para>
<para>
If an no error occurred in the last <acronym>SQL</acronym> statement.
<parameter>sqlca.sqlcode</parameter> will be 0 (<symbol>ECPG_NO_ERROR</>). If
<parameter>sqlca.sqlcode</parameter> is less that zero, this is a
serious error, like the database definition does not match the
query. If it is greater than zero, it is a normal error like the
table did not contain the requested row.
If no error occurred in the last <acronym>SQL</acronym> statement,
<literal>sqlca.sqlcode</literal> will be 0
(<symbol>ECPG_NO_ERROR</>). If <literal>sqlca.sqlcode</literal> is
less that zero, this is a serious error, like the database
definition does not match the query. If it is greater than zero, it
is a normal error like the table did not contain the requested row.
</para>
<para>
<parameter>sqlca.sqlerrm.sqlerrmc</parameter> will contain a string
<literal>sqlca.sqlerrm.sqlerrmc</literal> will contain a string
that describes the error. The string ends with the line number in
the source file.
</para>
......@@ -219,8 +434,8 @@ struct sqlca
<term><computeroutput>-12, Out of memory in line %d.</computeroutput></term>
<listitem>
<para>
Should not normally occur. This indicates your virtual memory is
exhausted.
Should not normally occur. This indicates your virtual memory
is exhausted.
</para>
</listitem>
</varlistentry>
......@@ -241,10 +456,10 @@ struct sqlca
<term><computeroutput>-201 (ECPG_TOO_MANY_ARGUMENTS): Too many arguments line %d.</computeroutput></term>
<listitem>
<para>
This means that <productname>PostgreSQL</productname> has
returned more arguments than we have matching variables.
Perhaps you have forgotten a couple of the host variables in
the <command>INTO :var1,:var2</command>-list.
This means that the server has returned more arguments than we
have matching variables. Perhaps you have forgotten a couple
of the host variables in the <command>INTO
:var1,:var2</command> list.
</para>
</listitem>
</varlistentry>
......@@ -253,11 +468,9 @@ struct sqlca
<term><computeroutput>-202 (ECPG_TOO_FEW_ARGUMENTS): Too few arguments line %d.</computeroutput></term>
<listitem>
<para>
This means that <productname>PostgreSQL</productname> has
returned fewer arguments than we have host variables. Perhaps
you have too many host variables in the <command>INTO
:var1,:var2</command>-list.
</para>
This means that the server has returned fewer arguments than we
have host variables. Perhaps you have too many host variables
in the <command>INTO :var1,:var2</command> list. </para>
</listitem>
</varlistentry>
......@@ -291,8 +504,8 @@ struct sqlca
<para>
This means the host variable is of type <type>unsigned
int</type> and the field in the
<productname>PostgreSQL</productname> database is of another type
and contains a value that cannot be interpreted as an
<productname>PostgreSQL</productname> database is of another
type and contains a value that cannot be interpreted as an
<type>unsigned int</type>. The library uses
<function>strtoul()</function> for this conversion.
</para>
......@@ -327,8 +540,8 @@ struct sqlca
<term><computeroutput>-208 (ECPG_EMPTY): Empty query line %d.</computeroutput></term>
<listitem>
<para>
<productname>PostgreSQL</productname> returned <symbol>PGRES_EMPTY_QUERY</symbol>, probably
because the query indeed was empty.
The query was empty. (This cannot normally happen in an
embedded SQL program, so it may point to an internal error.)
</para>
</listitem>
</varlistentry>
......@@ -337,8 +550,8 @@ struct sqlca
<term><computeroutput>-209 (ECPG_MISSING_INDICATOR): NULL value without indicator in line %d.</computeroutput></term>
<listitem>
<para>
<productname>PostgreSQL</productname> returned <symbol>ECPG_MISSING_INDICATOR</symbol>
because a NULL was returned and no NULL indicator variable was supplied.
A null value was returned and no null indicator variable was
supplied.
</para>
</listitem>
</varlistentry>
......@@ -347,9 +560,8 @@ struct sqlca
<term><computeroutput>-210 (ECPG_NO_ARRAY): Variable is not an array in line %d.</computeroutput></term>
<listitem>
<para>
<productname>PostgreSQL</productname> returned <symbol>ECPG_NO_ARRAY</symbol>
because an ordinary variable was used in a place that requires
an array.
An ordinary variable was used in a place that requires an
array.
</para>
</listitem>
</varlistentry>
......@@ -358,9 +570,8 @@ struct sqlca
<term><computeroutput>-211 (ECPG_DATA_NOT_ARRAY): Data read from backend is not an array in line %d.</computeroutput></term>
<listitem>
<para>
<productname>PostgreSQL</productname> returned <symbol>ECPG_DATA_NOT_ARRAY</symbol>
because the database returned an ordinary variable in a place
that requires array value.
The database returned an ordinary variable in a place that
requires array value.
</para>
</listitem>
</varlistentry>
......@@ -397,7 +608,8 @@ struct sqlca
<term><computeroutput>-240 (ECPG_UNKNOWN_DESCRIPTOR): Descriptor %s not found in line %d.</computeroutput></term>
<listitem>
<para>
The descriptor specified was not found. The statement you are trying to use has not been prepared.
The descriptor specified was not found. The statement you are
trying to use has not been prepared.
</para>
</listitem>
</varlistentry>
......@@ -444,8 +656,8 @@ struct sqlca
<term><computeroutput>-400 (ECPG_PGSQL): Postgres error: %s line %d.</computeroutput></term>
<listitem>
<para>
Some <productname>PostgreSQL</productname> error.
The message contains the error message from the
Some <productname>PostgreSQL</productname> error. The message
contains the error message from the
<productname>PostgreSQL</productname> backend.
</para>
</listitem>
......@@ -455,8 +667,8 @@ struct sqlca
<term><computeroutput>-401 (ECPG_TRANS): Error in transaction processing line %d.</computeroutput></term>
<listitem>
<para>
<productname>PostgreSQL</productname> signaled that we cannot start,
commit or rollback the transaction.
<productname>PostgreSQL</productname> signaled that we cannot
start, commit, or rollback the transaction.
</para>
</listitem>
</varlistentry>
......@@ -474,40 +686,9 @@ struct sqlca
<term><computeroutput>100 (ECPG_NOT_FOUND): Data not found line %d.</computeroutput></term>
<listitem>
<para>
This is a <quote>normal</quote> error that tells you that what you are querying cannot
be found or you are at the end of the cursor.
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</sect2>
</sect1>
<sect1 id="ecpg-limitations">
<title>Limitations</title>
<para>
What will never be included and why it cannot be done:
<variablelist>
<varlistentry>
<term>Oracle's single tasking</term>
<listitem>
<para>
Oracle version 7.0 on <systemitem class="osname">AIX</> 3 uses OS-supported locks in shared
memory that allow an application designer to link an application
in a <quote>single tasking</quote> way. Instead of starting one client
process per application process, both the database part and the
application part run in the same process. In later versions of
Oracle this is no longer supported.
</para>
<para>
This would require a total redesign of the
<productname>PostgreSQL</productname> access model and the
performance gain does not justify the effort.
This is a <quote>normal</quote> error that tells you that what
you are querying cannot be found or you are at the end of the
cursor.
</para>
</listitem>
</varlistentry>
......@@ -515,350 +696,229 @@ struct sqlca
</para>
</sect1>
<sect1 id="ecpg-porting">
<title>Porting From Other <acronym>RDBMS</acronym> Packages</title>
<sect1 id="ecpg-include">
<title>Including Files</title>
<para>
The design of <application>ecpg</application> follows the SQL
standard. Porting from a standard RDBMS should not be a problem.
Unfortunately there is no such thing as a standard RDBMS. Therefore
<application>ecpg</application> tries to understand syntax
extensions as long as they do not create conflicts with the
standard.
To include an external file into your embedded SQL program, use:
<programlisting>
EXEC SQL INCLUDE <replaceable>filename</replaceable>;
</programlisting>
The embedded SQL preprocessor will look for a file named
<literal><replaceable>filename</replaceable>.h</literal>,
preprocess it, and include it in the resulting C output. Thus,
embedded SQL statements in the included file are handled correctly.
</para>
<para>
The following list shows all the known incompatibilities. If you
find one not listed please notify the developers. Note, however, that
we list only incompatibilities from a precompiler of another RDBMS
to <application>ecpg</application> and not
<application>ecpg</application> features that these RDBMS do not
support.
Note that this is <emphasis>not</emphasis> the same as
<programlisting>
#include &lt;<replaceable>filename</replaceable>.h&gt;
</programlisting>
because the file would not be subject to SQL command preprocessing.
Naturally, you can continue to use the C
<literal>#include</literal> directive to include other header
files.
</para>
<note>
<para>
<variablelist>
<varlistentry>
<term>Syntax of FETCH</term>
<indexterm><primary>FETCH</><secondary>embedded SQL</></indexterm>
<listitem>
<para>
The standard syntax for FETCH is:
</para>
<para>
FETCH [direction] [amount] IN|FROM <replaceable>cursor</replaceable>.
</para>
<para>
<indexterm><primary>Oracle</></>
<application>Oracle</application>, however, does not use the keywords IN
or FROM. This feature cannot be added since it would create parsing
conflicts.
</para>
</listitem>
</varlistentry>
</variablelist>
The include file name is case-sensitive, even though the rest of
the <literal>EXEC SQL INCLUDE</literal> command follows the normal
SQL case-sensitivity rules.
</para>
</note>
</sect1>
<sect1 id="ecpg-develop">
<title>For the Developer</title>
<para>
This section explain how <application>ecpg</application>
works internally. It contains valuable information to help users
understand how to use <application>ecpg</application>.
</para>
<sect2>
<title>The Preprocessor</title>
<para>
The first four lines written by <command>ecpg</command> to the output are fixed lines.
Two are comments and two are include lines necessary to interface
to the library.
</para>
<sect1 id="ecpg-process">
<title>Processing Embedded SQL Programs</title>
<para>
Then the preprocessor reads through the file and writes output.
Normally it just echoes everything to the output.
Now that you have an idea how to form embedded SQL C programs, you
probably want to know how to compile them. Before compiling you
run the file through the embedded <acronym>SQL</acronym>
<acronym>C</acronym> preprocessor, which converts the
<acronym>SQL</acronym> statements you used to special function
calls. After compiling, you must link with a special library that
contains the needed functions. These functions fetch information
from the arguments, perform the <acronym>SQL</acronym> query using
the <application>libpq</application> interface, and put the result
in the arguments specified for output.
</para>
<para>
When it sees an <command>EXEC SQL</command> statement, it
intervenes and changes it. The <command>EXEC SQL</command>
statement can be one of these:
<variablelist>
<varlistentry>
<term>Declare sections</term>
<listitem>
<para>
<command>Declare</> sections begin with:
<programlisting>
exec sql begin declare section;
</programlisting>
and end with:
The preprocessor program is called <filename>ecpg</filename> and is
included in a normal PostgreSQL installation. Embedded SQL
programs are typically named with an extension
<filename>.pgc</filename>. If you have a program file called
<filename>prog1.pgc</filename>, you can preprocess it by simply
calling
<programlisting>
exec sql end declare section;
ecpg prog1.pgc
</programlisting>
In this section only variable declarations are allowed. Every
variable declared within this section is stored in a list
of variables indexed by name together with its corresponding
type.
</para>
<para>
In particular the definition of a structure or union also must
be listed inside a <command>declare</> section. Otherwise
<application>ecpg</application> cannot handle these types since
it does not know the definition.
This will create a file called <filename>prog1.c</filename>. If
your input files do not follow the suggested naming pattern, you
can specify the output file explicitly using the
<option>-o</option> option.
</para>
<para>
The declaration is also echoed to the file to make it a normal
C variable.
</para>
<para>
The special types <type>VARCHAR</type> and
<type>VARCHAR2</type> are converted into a named <type>struct</> for
every variable. A declaration like:
The preprocessed file can be compiled normally, for example
<programlisting>
VARCHAR var[180];
</programlisting>
is converted into:
<programlisting>
struct varchar_var { int len; char arr[180]; } var;
cc -c prog1.c
</programlisting>
The generated C source files include headers files from the
PostgreSQL installation, so if you installed PostgreSQL in a
location that is not searched by default, you have to add an option
such as <literal>-I/usr/local/pgsql/include</literal> to the
compilation command line.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Include statements</term>
<listitem>
<para>
An include statement looks like:
<programlisting>
exec sql include filename;
</programlisting>
Note that this is NOT the same as:
To link an embedded SQL program, you need to include the
<filename>libecpg</filename> library, like so:
<programlisting>
#include &lt;filename.h&gt;
cc -o myprog prog1.o prog2.o ... -lecpg
</programlisting>
Again, you might have to add an option like
<literal>-L/usr/local/pgsql/lib</literal> to that command line.
</para>
<para>
Instead the file specified is parsed by
<application>ecpg</application> so the contents of the file are
included in the resulting C code. This way you are able to
specify EXEC SQL commands in an include file.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Connect statement</term>
<listitem>
<para>
A connect statement looks like:
If you manage the build process of a larger project using
<application>make</application>, it may be convenient to include
the following implicit rule to your makefiles:
<programlisting>
exec sql connect to <replaceable>connection target</replaceable>;
ECPG = ecpg
%.c: %.pgc
$(ECPG) $<
</programlisting>
It creates a connection to the specified database.
</para>
<para>
The <replaceable>connection target</replaceable> can be specified in the
following ways:
<itemizedlist>
<listitem>
<simpara>
<literal>dbname[@server][:port][as <replaceable>connection
name</replaceable>][user <replaceable>user name</replaceable>]</literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal>tcp:postgresql://server[:port][/dbname][as
<replaceable>connection name</replaceable>][user <replaceable>user name</replaceable>]</literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal>unix:postgresql://server[:port][/dbname][as
<replaceable>connection name</replaceable>][user <replaceable>user name</replaceable>]</literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal><replaceable>character variable</replaceable>[as
<replaceable>connection name</replaceable>][user <replaceable>user name</replaceable>]</literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal><replaceable>character string</replaceable>[as
<replaceable>connection name</replaceable>][<replaceable>user</replaceable>]</literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal>default</literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal>user</literal>
</simpara>
</listitem>
</itemizedlist>
The complete syntax of the <command>ecpg</command> command is
detailed in &cite-reference;.
</para>
</sect1>
<sect1 id="ecpg-library">
<title>Library Functions</title>
<para>
There are also different ways to specify the user name:
The <filename>libecpg</filename> library primarily contains
<quote>hidden</quote> functions that are used to implement the
functionality expressed by the embedded SQL commands. But there
are some functions that can usefully be called directly. Note that
this makes your code unportable.
</para>
<itemizedlist>
<listitem>
<simpara>
<literal><replaceable>userid</replaceable></literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal><replaceable>userid</replaceable>/<replaceable>password</replaceable></literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal><replaceable>userid</replaceable> identified by <replaceable>password</replaceable></literal>
</simpara>
</listitem>
<listitem>
<simpara>
<literal><replaceable>userid</replaceable> using <replaceable>password</replaceable></literal>
</simpara>
</listitem>
</itemizedlist>
<para>
<function>ECPGdebug(int <replaceable>on</replaceable>, FILE
*<replaceable>stream</replaceable>)</function> turns on debug
logging if called with the first argument non-zero. Debug logging
is done on <replaceable>stream</replaceable>. Most
<acronym>SQL</acronym> statement log their arguments and results.
</para>
<para>
Finally, the <replaceable>userid</replaceable> and <replaceable>password</replaceable> may be a constant text, a
character variable, or a character string.
The most important function, <function>ECPGdo</function>, logs
all <acronym>SQL</acronym> statements with both the expanded
string, i.e. the string with all the input variables inserted,
and the result from the <productname>PostgreSQL</productname>
server. This can be very useful when searching for errors in your
<acronym>SQL</acronym> statements.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Disconnect statements</term>
<listitem>
<para>
A disconnect statement looks like:
<programlisting>
exec sql disconnect [<replaceable>connection target</replaceable>];
</programlisting>
It closes the connection to the specified database.
<function>ECPGstatus()</function> This method returns true if we
are connected to a database and false if not.
</para>
<para>
The <replaceable>connection target</replaceable> can be specified in the
following ways:
<itemizedlist>
<listitem>
<simpara>
<literal><replaceable>connection name</replaceable></literal>
</simpara>
</listitem>
</itemizedlist>
</sect1>
<listitem>
<simpara>
<literal>default</literal>
</simpara>
</listitem>
<sect1 id="ecpg-porting">
<title>Porting From Other <acronym>RDBMS</acronym> Packages</title>
<listitem>
<simpara>
<literal>current</literal>
</simpara>
</listitem>
<para>
The design of <application>ecpg</application> follows the SQL
standard. Porting from a standard RDBMS should not be a problem.
Unfortunately there is no such thing as a standard RDBMS. Therefore
<application>ecpg</application> tries to understand syntax
extensions as long as they do not create conflicts with the
standard.
</para>
<listitem>
<simpara>
<literal>all</literal>
</simpara>
</listitem>
</itemizedlist>
<para>
The following list shows all the known incompatibilities. If you
find one not listed please notify the developers. Note, however,
that we list only incompatibilities from a preprocessor of another
RDBMS to <application>ecpg</application> and not
<application>ecpg</application> features that these RDBMS do not
support.
</para>
</listitem>
</varlistentry>
<variablelist>
<varlistentry>
<term>Open cursor statement</term>
<term>Syntax of <command>FETCH</command></term>
<indexterm><primary>FETCH</><secondary>embedded SQL</></indexterm>
<listitem>
<para>
An open cursor statement looks like:
<programlisting>
exec sql open <replaceable>cursor</replaceable>;
</programlisting>
and is not copied to the output. Instead, the cursor's
<command>DECLARE</> command is used because it opens the cursor
as well.
The standard syntax for <command>FETCH</command> is:
<synopsis>
FETCH <optional><replaceable>direction</></> <optional><replaceable>amount</></> IN|FROM <replaceable>cursor</replaceable>
</synopsis>
<indexterm><primary>Oracle</></>
<application>Oracle</application>, however, does not use the
keywords <literal>IN</literal> or <literal>FROM</literal>. This
feature cannot be added since it would create parsing conflicts.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect1>
<sect1 id="ecpg-develop">
<title>For the Developer</title>
<varlistentry>
<term>Commit statement</term>
<listitem>
<para>
A commit statement looks like:
<programlisting>
exec sql commit;
</programlisting>
This section explain how <application>ecpg</application> works
internally. This information can occasionally be useful to help
users understand how to use <application>ecpg</application>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Rollback statement</term>
<listitem>
<sect2>
<title>The Preprocessor</title>
<para>
A rollback statement looks like:
<programlisting>
exec sql rollback;
</programlisting>
The first four lines written by <command>ecpg</command> to the
output are fixed lines. Two are comments and two are include
lines necessary to interface to the library. Then the
preprocessor reads through the file and writes output. Normally
it just echoes everything to the output.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Other statements</term>
<listitem>
<para>
Other <acronym>SQL</acronym> statements are used by
starting with <command>exec sql</command> and ending with
<command>;</command>. Everything in between is treated as an
<acronym>SQL</acronym> statement and parsed for variable
substitution.
When it sees an <command>EXEC SQL</command> statement, it
intervenes and changes it. The command starts with <command>exec
sql</command> and ends with <command>;</command>. Everything in
between is treated as an <acronym>SQL</acronym> statement and
parsed for variable substitution.
</para>
<para>
Variable substitution occurs when a symbol starts with a colon
(<command>:</command>). The variable with that name is looked
up among the variables that were previously declared within a
<command>declare</> section. Depending on whether the variable is
being use for input or output, a pointer to the variable is
output to allow access by the function.
(<literal>:</literal>). The variable with that name is looked up
among the variables that were previously declared within a
<literal>EXEC SQL DECLARE</> section. Depending on whether the
variable is being use for input or output, a pointer to the
variable is output to allow access by the function.
</para>
<para>
......@@ -904,13 +964,14 @@ exec sql rollback;
<listitem>
<para>
A pointer to the value of the indicator variable or a pointer to the pointer of the indicator variable.
A pointer to the value of the indicator variable or a pointer
to the pointer of the indicator variable.
</para>
</listitem>
<listitem>
<para>
0.
0
</para>
</listitem>
......@@ -929,25 +990,28 @@ exec sql rollback;
</itemizedlist>
</para>
</listitem>
</varlistentry>
</variablelist>
<para>
Note that not all SQL commands are treated in this way. For
instance, an open cursor statement like
<programlisting>
EXEC SQL OPEN <replaceable>cursor</replaceable>;
</programlisting>
is not copied to the output. Instead, the cursor's
<command>DECLARE</> command is used because it opens the cursor as
well.
</para>
</sect2>
<sect2>
<title>A Complete Example</title>
<para>
Here is a complete example describing the output of the preprocessor of a
file <filename>foo.pgc</filename>:
Here is a complete example describing the output of the
preprocessor of a file <filename>foo.pgc</filename> (details may
change with each particular version of the preprocessor):
<programlisting>
exec sql begin declare section;
EXEC SQL BEGIN DECLARE SECTION;
int index;
int result;
exec sql end declare section;
EXEC SQL END DECLARE SECTION;
...
exec sql select res into :result from mytable where index = :index;
EXEC SQL SELECT res INTO :result FROM mytable WHERE index = :index;
</programlisting>
is translated into:
<programlisting>
......@@ -964,7 +1028,7 @@ exec sql select res into :result from mytable where index = :index;
int result;
/* exec sql end declare section */
...
ECPGdo(__LINE__, NULL, "select res from mytable where index = ? ",
ECPGdo(__LINE__, NULL, "SELECT res FROM mytable WHERE index = ? ",
ECPGt_int,&amp;(index),1L,1L,sizeof(int),
ECPGt_NO_INDICATOR, NULL , 0L, 0L, 0L, ECPGt_EOIT,
ECPGt_int,&amp;(result),1L,1L,sizeof(int),
......@@ -982,9 +1046,10 @@ ECPGdo(__LINE__, NULL, "select res from mytable where index = ? ",
<para>
The most important function in the library is
<function>ECPGdo</function>. It takes a variable number of
arguments. Hopefully there are no computers that limit the
number of variables that can be accepted by a <function>varargs()</function> function. This
can easily add up to 50 or so arguments.
arguments. Hopefully there are no computers that limit the number
of variables that can be accepted by a
<function>varargs()</function> function. This can easily add up to
50 or so arguments.
</para>
<para>
......@@ -995,7 +1060,8 @@ ECPGdo(__LINE__, NULL, "select res from mytable where index = ? ",
<term>A line number</term>
<listitem>
<para>
This is a line number of the original line; used in error messages only.
This is a line number of the original line; used in error
messages only.
</para>
</listitem>
</varlistentry>
......@@ -1017,8 +1083,8 @@ ECPGdo(__LINE__, NULL, "select res from mytable where index = ? ",
<term>Input variables</term>
<listitem>
<para>
As described in the section about the preprocessor, every input variable
gets ten arguments.
As described in the section about the preprocessor, every
input variable gets ten arguments.
</para>
</listitem>
</varlistentry>
......@@ -1027,7 +1093,8 @@ ECPGdo(__LINE__, NULL, "select res from mytable where index = ? ",
<term><parameter>ECPGt_EOIT</></term>
<listitem>
<para>
An <type>enum</> telling that there are no more input variables.
An <type>enum</> telling that there are no more input
variables.
</para>
</listitem>
</varlistentry>
......@@ -1036,8 +1103,9 @@ ECPGdo(__LINE__, NULL, "select res from mytable where index = ? ",
<term>Output variables</term>
<listitem>
<para>
As described in the section about the preprocessor, every input variable
gets ten arguments. These variables are filled by the function.
As described in the section about the preprocessor, every
input variable gets ten arguments. These variables are filled
by the function.
</para>
</listitem>
</varlistentry>
......@@ -1052,21 +1120,9 @@ ECPGdo(__LINE__, NULL, "select res from mytable where index = ? ",
</varlistentry>
</variablelist>
</para>
<para>
In the default mode, queries are committed only when <command>exec
sql commit</command> is issued. <application>Ecpg</application>
also supports auto-commit of transactions via the
<option>-t</option> command-line option or via the <literal>exec
sql set autocommit to on</literal> statement. In
<literal>autocommit</literal> mode, each query is automatically
committed unless it is inside an explicit transaction block. This
mode can be explicitly turned off using <literal>exec sql set
autocommit to off</literal>.
</para>
</sect2>
</sect1>
</chapter>
</chapter>
<!-- Keep this comment at the end of the file
Local variables:
......
doc/src/sgml/ref/ecpg-ref.sgml
View file @ cc4f5769
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/ecpg-ref.sgml,v 1.20 2002/07/28 15:22:20 petere Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/ref/ecpg-ref.sgml,v 1.21 2002/10/21 18:04:05 petere Exp $
PostgreSQL documentation
-->
<refentry id="APP-ECPG">
<refmeta>
<refentrytitle id="app-ecpg-title"><application>ecpg</application></refentrytitle>
<refentrytitle><application>ecpg</application></refentrytitle>
<manvolnum>1</manvolnum>
<refmiscinfo>Application</refmiscinfo>
</refmeta>
<refnamediv>
<refname>
<application>ecpg</application>
</refname>
<refpurpose>
embedded SQL C preprocessor
</refpurpose>
<refname><application>ecpg</application></refname>
<refpurpose>embedded SQL C preprocessor</refpurpose>
</refnamediv>
<refsynopsisdiv>
<refsynopsisdivinfo>
<date>1999-07-20</date>
</refsynopsisdivinfo>
<cmdsynopsis>
<command>ecpg</command>
<arg choice="opt">-v</arg>
<arg choice="opt">-t</arg>
<arg choice="opt">-I <replaceable>include-path</replaceable></arg>
<arg choice="opt">-o <replaceable>outfile</replaceable></arg>
<arg choice="opt" rep="repeat"><replaceable>option</replaceable></arg>
<arg choice="plain" rep="repeat"><replaceable>file</replaceable></arg>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1 id="APP-ECPG-description">
<title>Description</title>
<para>
<application>ecpg</application>
is an embedded SQL preprocessor for the C language and the
<productname>PostgreSQL</productname>. It
enables development of C programs with embedded SQL code.
<command>ecpg</command> is the embedded SQL preprocessor for C
programs. It converts C programs with embedded SQL statements to
normal C code by replacing the SQL invocations with special
function calls. The output files can then be processed with any C
compiler tool chain.
</para>
<para>
Linus Tolke (<email>linus@epact.se</email>) was the
original author of <application>ecpg</application> (up to version 0.2).
Michael Meskes (<email>meskes@debian.org</email>)
is the current author and maintainer of <application>ecpg</application>.
Thomas Good (<email>tomg@q8.nrnet.org</email>)
is the author of the last revision of the <application>ecpg</application> man page, on which
this document is based.
<command>ecpg</command> will convert each input file given on the
command line to the corresponding C output file. Input files
preferrably have the extension <filename>.pgc</filename>, in which
case the extension will be replaced by <filename>.c</filename> to
determine the output file name. If the extension of the input file
is not <filename>.pgc</filename>, then the output file name is
computed by appending <literal>.c</literal> to the full file name.
The output file name can also be overridden using the
<option>-o</option> option.
</para>
<para>
This reference page does not describe the embedded SQL language.
See &cite-programmer; for that.
</para>
</refsect1>
......@@ -59,338 +58,137 @@ PostgreSQL documentation
<title>Options</title>
<para>
<application>ecpg</application> accepts the following command
line arguments:
<command>ecpg</command> accepts the following command-line
arguments:
<variablelist>
<varlistentry>
<term>-v</term>
<term><option>-c</option></term>
<listitem>
<para>
Print version information.
Automatically generate C code from SQL code. Currently, this
works for <literal>EXEC SQL TYPE</literal>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-t</term>
<term><option>-D <replaceable>symbol</replaceable></option></term>
<listitem>
<para>
Turn on auto-commit of transactions. In this mode, each query is
automatically committed unless it is inside an explicit
transaction block. In the default mode, queries are committed
only when <command>exec sql commit</command> is issued.
Define a C preprocessor symbol.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-I <replaceable class="parameter">include-path</replaceable></term>
<term><option>-I <replaceable class="parameter">directory</replaceable></option></term>
<listitem>
<para>
Specify an additional include path.
Defaults are <filename>.</filename> (current directory),
Specify an additional include path, used to find files included
via <literal>EXEC SQL INCLUDE</literal>. Defaults are
<filename>.</filename> (current directory),
<filename>/usr/local/include</filename>, the
<productname>PostgreSQL</productname> include path which is
defined at compile time (default:
<productname>PostgreSQL</productname> include directory which
is defined at compile time (default:
<filename>/usr/local/pgsql/include</filename>), and
<filename>/usr/include</filename>.
<filename>/usr/include</filename>, in that order.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>-o <replaceable>outfile</replaceable></term>
<term><option>-o <replaceable>filename</replaceable></option></term>
<listitem>
<para>
Specifies that <application>ecpg</application> should write all its output to <replaceable>outfile</replaceable>.
If no such option is given the output is written to
<filename><replaceable>name</replaceable>.c</filename>,
assuming the input file was
named <filename><replaceable>name</replaceable>.pgc</filename>.
If the input file does have the expected
<literal>.pgc</literal> suffix, then the output file will have
<literal>.pgc</literal> appended to the input file name.
Specifies that <application>ecpg</application> should write all
its output to the given <replaceable>filename</replaceable>.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><replaceable class="parameter">file</replaceable></term>
<term><option>-t</option></term>
<listitem>
<para>
The files to be processed.
Turn on autocommit of transactions. In this mode, each query is
automatically committed unless it is inside an explicit
transaction block. In the default mode, queries are committed
only when <command>EXEC SQL COMMIT</command> is issued.
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</refsect1>
<refsect1>
<title>Exit Status</title>
<varlistentry>
<term><option>-v</option></term>
<listitem>
<para>
<application>ecpg</application> returns 0 to the shell on
successful completion, non-zero for errors.
Print additional information including the version and the
include path.
</para>
</refsect1>
<refsect1>
<title>Usage</title>
<refsect2 id="APP-ECPG-preprocessing">
<title>Preprocessing for Compilation</title>
</listitem>
</varlistentry>
<varlistentry>
<term><option>---help</option></term>
<listitem>
<para>
An embedded SQL source file must be preprocessed before
compilation:
<synopsis>
ecpg [ -d ] [ -o <replaceable>file</replaceable> ] <replaceable>file</replaceable>.pgc
</synopsis>
where the optional <option>-d</option> flag turns on debugging.
The <literal>.pgc</literal> extension is an
arbitrary means of denoting <application>ecpg</application> source.
Show a brief summary of the command usage, then exit.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><option>--version</option></term>
<listitem>
<para>
You may want to redirect the preprocessor output to a log file.
Output version information, then exit.
</para>
</refsect2>
<refsect2 id="APP-ECPG-compiling">
<title>Compiling and Linking</title>
<para>
Assuming the <productname>PostgreSQL</productname> binaries are in
<filename>/usr/local/pgsql</filename>, you will need to compile
and link your preprocessed source file:
<synopsis>
gcc -g -I /usr/local/pgsql/include [ -o <replaceable>file</replaceable> ] <replaceable>file</replaceable>.c -L /usr/local/pgsql/lib -lecpg -lpq
</synopsis>
</listitem>
</varlistentry>
</variablelist>
</para>
</refsect2>
</refsect1>
<refsect1 id="APP-ECPG-grammar">
<title>Grammar</title>
<refsect2 id="APP-ECPG-library">
<title>Libraries</title>
<para>
The preprocessor will prepend two directives to the source:
<programlisting>
#include &lt;ecpgtype.h&gt;
#include &lt;ecpglib.h&gt;
</programlisting>
</para>
</refsect2>
<refsect2 id="APP-ecpg-declaration">
<title>Variable Declaration</title>
<para>
Variables declared within <application>ecpg</application> source code must be prepended with:
<programlisting>
EXEC SQL BEGIN DECLARE SECTION;
</programlisting>
</para>
<para>
Similarly, variable declaration sections must terminate with:
<programlisting>
EXEC SQL END DECLARE SECTION;
</programlisting>
<note>
<para>
Prior to version 2.1.0, each variable had to be declared
on a separate line. As of version 2.1.0 multiple variables may
be declared on a single line:
<programlisting>
char foo[16], bar[16];
</programlisting>
</para>
</note>
</para>
</refsect2>
<refsect2 id="APP-ECPG-errors">
<title>Error Handling</title>
<para>
The SQL communication area is defined with:
<programlisting>
EXEC SQL INCLUDE sqlca;
</programlisting>
</para>
<note>
<para>
The <literal>sqlca</literal> is in lowercase.
While SQL convention may be
followed, i.e., using uppercase to separate embedded SQL
from C statements, <literal>sqlca</literal> (which includes the <filename>sqlca.h</>
header file) <emphasis>must</> be lowercase. This is because the
EXEC SQL prefix indicates that this inclusion will be parsed by
<application>ecpg</application>.
<application>ecpg</application> observes case sensitivity
(<filename>SQLCA.h</> will not be found).
<command>EXEC SQL INCLUDE</command>
can be used to include other header files
as long as case sensitivity is observed.
</para>
</note>
<para>
The <literal>sqlprint</literal> command is used with the <literal>EXEC SQL WHENEVER</literal>
statement to turn on error handling throughout the
program:
<programlisting>
EXEC SQL WHENEVER sqlerror sqlprint;
</programlisting>
and
<programlisting>
EXEC SQL WHENEVER not found sqlprint;
</programlisting>
</para>
<note>
<para>
This is <emphasis>not</emphasis> an exhaustive example of usage for
the <command>EXEC SQL WHENEVER</command> statement.
Further examples of usage may
be found in SQL manuals (e.g., <citetitle>The LAN TIMES Guide to SQL</> by
Groff and Weinberg).
</para>
</note>
</refsect2>
<refsect2 id="APP-ECPG-connecting">
<title>Connecting to the Database Server</title>
<para>
One connects to a database using the following:
<programlisting>
EXEC SQL CONNECT TO <replaceable>dbname</replaceable>;
</programlisting>
where the database name is not quoted. Prior to version 2.1.0, the
database name was required to be inside single quotes.
</para>
<para>
Specifying a server and port name in the connect statement is also
possible. The syntax is:
<synopsis>
<replaceable>dbname</replaceable>[@<replaceable>server</replaceable>][:<replaceable>port</replaceable>]
</synopsis>
or
<synopsis>
&lt;tcp|unix&gt;:postgresql://<replaceable>server</replaceable>[:<replaceable>port</replaceable>][/<replaceable>dbname</replaceable>][?<replaceable>options</replaceable>]
</synopsis>
</para>
</refsect2>
<refsect2 id="APP-ECPG-queries">
<title>Queries</title>
<para>
In general, SQL queries acceptable to other applications such as
<application>psql</application> can be embedded into your C
code. Here are some examples of how to do that.
</para>
<refsect1>
<title>Notes</title>
<para>
Create Table:
<programlisting>
EXEC SQL CREATE TABLE foo (number int4, ascii char(16));
EXEC SQL CREATE UNIQUE index num1 on foo(number);
EXEC SQL COMMIT;
</programlisting>
When compiling the preprocessed C code files, the compiler needs to
be able to find the <application>ECPG</> header files in the
PostgreSQL include directory. Therefore, one might have to use the
<option>-I</> option when invoking the compiler (e.g.,
<literal>-I/usr/local/pgsql/include</literal>).
</para>
<para>
Insert:
<programlisting>
EXEC SQL INSERT INTO foo (number, ascii) VALUES (9999, 'doodad');
EXEC SQL COMMIT;
</programlisting>
Programs using C code with embedded SQL have to be linked against
the <filename>libecpg</filename> library, for example using the
flags <literal>-L/usr/local/pgsql/lib -lecpg</literal>.
</para>
<para>
Delete:
<programlisting>
EXEC SQL DELETE FROM foo WHERE number = 9999;
EXEC SQL COMMIT;
</programlisting>
</para>
<para>
Singleton Select:
<programlisting>
EXEC SQL SELECT foo INTO :FooBar FROM table1 WHERE ascii = 'doodad';
</programlisting>
The value of either of these directories that is appropriate for
the installation can be found out using <xref
linkend="app-pgconfig">.
</para>
</refsect1>
<para>
Select using Cursors:
<programlisting>
EXEC SQL DECLARE foo_bar CURSOR FOR
SELECT number, ascii FROM foo
ORDER BY ascii;
EXEC SQL FETCH foo_bar INTO :FooBar, DooDad;
...
EXEC SQL CLOSE foo_bar;
EXEC SQL COMMIT;
</programlisting>
</para>
<refsect1>
<title>Examples</title>
<para>
Updates:
If you have an embedded SQL C source file named
<filename>prog1.pgc</filename>, you can create an executable
program using the following sequence of commands:
<programlisting>
EXEC SQL UPDATE foo
SET ascii = 'foobar'
WHERE number = 9999;
EXEC SQL COMMIT;
ecpg prog1.pgc
cc -I/usr/local/pgsql/include -c prog1.c
cc -o prog1 prog1.o -L/usr/local/pgsql/lib -lecpg
</programlisting>
</para>
</refsect2>
</refsect1>
<refsect1 id="APP-ECPG-notes">
<title>Notes</title>
<para>
The complete structure definition MUST be listed
inside the declare section.
</para>
<para>
See the <filename>TODO</filename> file in the source for some more
missing features.
</para>
</refsect1>
......@@ -399,7 +197,7 @@ EXEC SQL COMMIT;
<para>
<citetitle>PostgreSQL Programmer's Guide</citetitle> for a more
detailed description of the embedded SQL interface.
detailed description of the embedded SQL interface
</para>
</refsect1>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment