Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67837
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.49 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
Date: Wed, 26 Jun 2013 07:44:06 +0900
Message-ID: <CAGa2bXYbo++wkYynN+SZ0bDZQjrvu+Q-CeEDh+9nWCfyt4K5jg@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c3ca14a57f6f04e0024653
Subject: pgsql: Binary data support improvement
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a11c3ca14a57f6f04e0024653
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

Current pgsql module lacks direct binary support. Therefore, users have to
use pg_escape_bytea/pg_unescape_bytea for binary handling even with
prepared statement type APIs. Use of
pg_escape_bytea/pg_unescape_bytea requires some overheads on both server
and client side.

Following patch enables pg_execute() to handle binary directly.
https://github.com/yohgaki/php-src/compare/pgsql_binary_support
NOTE: This patch is only for PoC and treats all parameters as binary,
returns binary result ALWAYS. i.e. Not only bytea, but int, float, numeric,
etc are returned as binary.

I'm planning to add $params_format(array) and $binary_result(bool)
parameter.
pg_execute() will look like

Current:
resource pg_execute ([ resource $connection ], string $stmtname , array
$params )

New:
resource pg_execute ([ resource $connection ], string $stmtname , array
$params [, array $params_format [, bool $binary_result]] )

Any thoughts?

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a11c3ca14a57f6f04e0024653--