Chages for new pg_last_notice()

Print PostgreSQL version number in phpinfo()

Clean up code.
Removed PHP_PGSQL_API macro.
Define pgsql_globals_id
# Need a little more clean up

Make module specified functions to static.
Added TSRMLS_D/C, get rid of one TSRMLS_FETCH.

Added "auto_reset_presistent" ini entry.

Funtion rename:
Functions are renamed accoding to coding stanard. Some functions has
completely different name now.
New functions:
pg_copy_to()/pg_copy_from() - by Youichi Iwakiri <yi

Funtion rename:
Functions are renamed accoding to coding stanard. Some functions has
completely different name now.
New functions:
pg_copy_to()/pg_copy_from() - by Youichi Iwakiri <yiwakiri@st.rim.or.jp>
pg_lo_tell()/pg_lo_seek()/pg_result_error()/pg_result_status()
pg_escape_string()/pg_escape_bytea() - Only pgsql 7.2 or later.
Fixed:
Wrong mode when clean up connection resource.
Compiler warning for pg_encoding_to_char().
# Please do not document new functions, yet.
# For new functions and other info, please read README
# in module dir.

show more ...

Update headers.

Added async query functions

Fix pg_last_notice()

Redesigned thread safety mechanism - nua nua

Allow the PostgreSQL driver to do internal row counting when iterating
through a result set.

Submitted by: Georg von Zezschwitz <gvz@2scale.net>

Add pg_last_notice() function

make it compile with 6.5.x
postgresql notices are now send to the standard error-log

- Fix copyright notices with 2001

Simpler fix for the InvalidOid thing by Tom Lane.

He assured me that InvalidOid has always expanded to (Oid) 0, so this
should be safe.

Fix incompatibility with PostgreSQL CVS.

We now perform a check whether we need to include <postgres.h> to
succesfully compile.

PR: #9328

@- PostgreSQL now does a rollback at the end of a request on every
@ persistent connection. This is done by doing an "empty" transaction
@ on the connection (This was advised by someone fro

@- PostgreSQL now does a rollback at the end of a request on every
@ persistent connection. This is done by doing an "empty" transaction
@ on the connection (This was advised by someone from the PostgreSQL
@ core-team). If you leave transactions open on your page you will see a
@ "NOTICE: BEGIN: already a transaction in progress" message in your
@ apache error_log. This message is created by the PostgreSQL libs - we can
@ do nothing about it. (Thies)

show more ...

- Added the pg_lolseek function, which allows for arbitrary seeking within
a large object, and the pg_lotell call, which can be used to find the
current file offset for a large object (Su

- Added the pg_lolseek function, which allows for arbitrary seeking within
a large object, and the pg_lotell call, which can be used to find the
current file offset for a large object (Submitted by: Adam Haberlach
<adam@newsnipple.com>).
@- Added the pg_lolseek and pg_lotell functions (Derick)

show more ...

Changing my email address...

- The Sprit of PHP is to have descriptive function names and not
necessarily short ones. Maybe we should have some FAQ for this?

updated some functions'name using obsolete name convention.

- Renamed functions so that this extension finally starts to follow the
recommended naming scheme of PHP.

- Added functions pg_putline and pg_endcopy (thanks to Dirk Elmendorf
<delmendo@rackspace.com>)
@ Added functions pg_putline and pg_endcopy (Dirk Elmendorf)

This should fix #5826.

Change header protection macros to conform to standard.

Draft 3 of IEEE 1003.1 200x, "2.2 The Compilation Environment"

All identifiers that begin with an underscore and either an

Change header protection macros to conform to standard.

Draft 3 of IEEE 1003.1 200x, "2.2 The Compilation Environment"

All identifiers that begin with an underscore and either an uppercase
letter or another underscore are always reserved for any use by the
implementation.

show more ...