PEAR is archived and read-only

This mirror preserves historical PEAR package releases and metadata so existing references remain available.

Home » Database » DB » Bug #4736

PostgreSQL function names will be changed in 4.2.0 release to confirm to curren

Details

Submitted2005-07-04 09:41 UTC
Fromh dot danes at intermax dot nl
StatusWont fix
PackageDB
PHP Version5.0.4
OSLinux Redhat
Roadmaps(Not assigned)

Comments

[2005-07-04 09:41 UTC] h dot danes at intermax dot nl

Description:
------------
The PEAR DB Layer for PostgreSQL (version 1.7.6) use deprecated pgsql functions.

Source: http://nl2.php.net/manual/en/ref.pgsql.php

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.

Table 2. Function names changed
================================
Old name -> New name
pg_cmdtuples() pg_affected_rows()
pg_errormessage() pg_last_error()
pg_exec() pg_query()
pg_fieldname() pg_field_name()
pg_fieldsize() pg_field_size()
pg_fieldnum() pg_field_num()
pg_fieldprtlen() pg_field_prtlen()
pg_fieldisnull() pg_field_is_null()
pg_freeresult() pg_free_result()
pg_getlastoid() pg_last_oid()
pg_loreadall() pg_lo_read_all()
pg_locreate() pg_lo_create()
pg_lounlink() pg_lo_unlink()
pg_loopen() pg_lo_open()
pg_loclose() pg_lo_close()
pg_loread() pg_lo_read()
pg_lowrite() pg_lo_write()
pg_loimport() pg_lo_import()
pg_loexport() pg_lo_export()
pg_numrows() pg_num_rows()
pg_numfields() pg_num_fields()
pg_result() pg_fetch_result()

Actual result:
--------------
Errormessage: pg_exec() [function.pg-exec]: