ID: 21248 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Assigned +Status: Won\'t fix Bug Type: PostgreSQL related Operating System: Linux2.4 PHP Version: 4.3.0 Assigned To: yohgaki New Comment:
I would not like to add php own libpq function clone for following reasons. - Users are supposed to use libpq that matches backend - There is no use of pg_(un)escape_bytea function prior to 7.2 - Users should be able to use addslashes() to escape strings. (Only a little inefficient and does not work for certain encodings. But these problematic encodings do not work with PHP anyway) Extream case is PostgreSQL 7.3.x. It cannot even connect to older versions of backends. Use the libpq that comes from backend. (Use the same major/minor version at least. You may use different patch level releases between client and backend) Since bytea is almost useless without unescape function, I added pg_unescape_bytea() using locally implemented unescape bytea function for 7.2 users and it's available from 4.3.0. (The unescape function is more efficient than original version, too :) Previous Comments: ------------------------------------------------------------------------ [2002-12-28 10:19:11] [EMAIL PROTECTED] the postgresql module compiles for php, perfectly. but PQescapeBytea and PQescapeString is not available on all system, I don't know why, it's libpq's fault. php is linked dynamically with libpq, and PQescapeBytea is used by php. So apache cannot load the php module, due to an unresolved symbol(PQescapeBytea). if PQescapeBytea doesn't available on a system php should use an own implementation. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=21248&edit=1
