diff --git a/reference/pgsql/constants.xml b/reference/pgsql/constants.xml new file mode 100644 index 0000000000..172f7c5634 --- /dev/null +++ b/reference/pgsql/constants.xml @@ -0,0 +1,227 @@ + + +
+ &reftitle.constants; + &extension.constants; + + + + PGSQL_ASSOC + (integer) + + + + + + + + + + PGSQL_NUM + (integer) + + + + + + + + + + PGSQL_BOTH + (integer) + + + + + + + + + + PGSQL_CONNECTION_BAD + (integer) + + + + + + + + + + PGSQL_CONNECTION_OK + (integer) + + + + + + + + + + PGSQL_SEEK_SET + (integer) + + + + + + + + + + PGSQL_SEEK_CUR + (integer) + + + + + + + + + + PGSQL_SEEK_END + (integer) + + + + + + + + + + PGSQL_ESCAPE_STRING + (integer) + + + + + + + + + + PGSQL_ESCAPE_BYTEA + (integer) + + + + + + + + + + PGSQL_EMPTY_QUERY + (integer) + + + + + + + + + + PGSQL_COMMAND_OK + (integer) + + + + + + + + + + PGSQL_TUPLES_OK + (integer) + + + + + + + + + + PGSQL_COPY_OUT + (integer) + + + + + + + + + + PGSQL_COPY_IN + (integer) + + + + + + + + + + PGSQL_BAD_RESPONSE + (integer) + + + + + + + + + + PGSQL_NONFATAL_ERROR + (integer) + + + + + + + + + + PGSQL_FATAL_ERROR + (integer) + + + + + + + + +
+ + diff --git a/reference/pgsql/reference.xml b/reference/pgsql/reference.xml index 1968ef637b..19286ebc54 100644 --- a/reference/pgsql/reference.xml +++ b/reference/pgsql/reference.xml @@ -1,51 +1,72 @@ - + PostgreSQL functions PostgreSQL - - Postgres, developed originally in the UC Berkeley Computer Science - Department, pioneered many of the object-relational concepts now - becoming available in some commercial databases. It provides - SQL92/SQL99 language support, transaction integrity and type - extensibility. PostgreSQL is an open source descendant of this - original Berkeley code. - - - PostgreSQL database is Open Source product and available without - cost. To use PostgreSQL support, you need PostgreSQL 6.5 or - later. PostgreSQL 7.0 or later to enable all PostgreSQL module - feature. PostgreSQL supports many character encoding including - multibyte character encoding. The current version and more - information about PostgreSQL is available at &url.pgsql;. - - - In order to enable PostgreSQL support, - is required when you compile - PHP. If shared object module is available, PostgreSQL module may - be loaded using extension - directive in &php.ini; or dl - function. Supported ini directives are described in - php.ini-dist which comes with source distribution. - - +
+ &reftitle.intro; - Using the PostgreSQL module with PHP 4.0.6 is not recommended due to - a bug in the notice message handling code. Use 4.1.0 or later. + PostgreSQL database is Open Source product and available without + cost. Postgres, developed originally in the UC Berkeley Computer Science + Department, pioneered many of the object-relational concepts now + becoming available in some commercial databases. It provides + SQL92/SQL99 language support, transaction integrity and type + extensibility. PostgreSQL is an open source descendant of this + original Berkeley code. - - +
+ +
+ &reftitle.required; - PostgreSQL function names will be changed in 4.2.0 release to - confirm to current coding standards. Most of new names will have - additional underscores, e.g. pg_lo_open(). Some functions are - renamed to different name for consistency. e.g. pg_exec() to - pg_query(). Older names can be used in 4.2.0 and a few releases - from 4.2.0, but they may be deleted in the future. + To use PostgreSQL support, you need PostgreSQL 6.5 or + later, PostgreSQL 7.0 or later to enable all PostgreSQL module + features. PostgreSQL supports many character encoding including + multibyte character encoding. The current version and more + information about PostgreSQL is available at &url.pgsql;. +
+ +
+ &reftitle.install; + + In order to enable PostgreSQL support, + is required when you compile + PHP. If shared object module is available, PostgreSQL module may + be loaded using extension + directive in &php.ini; or dl + function. + +
+ +
+ &reftitle.runtime; + + Supported ini directives are described in + php.ini-dist which comes with source distribution. + +
+ +
+ How to use and hints + + + Using the PostgreSQL module with PHP 4.0.6 is not recommended due to + a bug in the notice message handling code. Use 4.1.0 or later. + + + + + PostgreSQL function names will be changed in 4.2.0 release to + confirm to current coding standards. Most of new names will have + additional underscores, e.g. pg_lo_open(). Some functions are + renamed to different name for consistency. e.g. pg_exec() to + pg_query(). Older names can be used in 4.2.0 and a few releases + from 4.2.0, but they may be deleted in the future. + Function names changed @@ -174,9 +195,9 @@ - Postmaster - PHP - Status + Postmaster + PHP + Status @@ -251,24 +272,30 @@ PGCLIENTENCODING=EUC-JP export PGHOST PGPORT PGDATABASE PGUSER PGPASSWORD PGDATESTYLE PGTZ PGCLIENTENCODING ]]> - - - - Starting with PostgreSQL 7.1.0, you can store up to 1GB into a - field of type text. In older versions, this was limited to the block - size (default was 8KB, maximum was 32KB, defined at compile time) - - - To use the large object (lo) interface, it is required to enclose - large object functions within a transaction block. A transaction - block starts with a SQL statement BEGIN and if - the transaction was valid ends with COMMIT or - END. If the transaction fails the transaction - should be closed with ROLLBACK or - ABORT. - - Using Large Objects - + + + + + &reference.pgsql.constants; + +
+ &reftitle.examples; + + Starting with PostgreSQL 7.1.0, you can store up to 1GB into a + field of type text. In older versions, this was limited to the block + size (default was 8KB, maximum was 32KB, defined at compile time) + + + To use the large object (lo) interface, it is required to enclose + large object functions within a transaction block. A transaction + block starts with a SQL statement BEGIN and if + the transaction was valid ends with COMMIT or + END. If the transaction fails the transaction + should be closed with ROLLBACK or + ABORT. + + Using Large Objects + ]]> - - - You should not close the connection to the PostgreSQL server - before closing the large object. - + + + You should not close the connection to the PostgreSQL server + before closing the large object. + +
&reference.pgsql.functions;