Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:67851
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.47 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <51CAB115.60602@beccati.com>
References: <CAGa2bXYbo++wkYynN+SZ0bDZQjrvu+Q-CeEDh+9nWCfyt4K5jg@mail.gmail.com>
 <51CAB115.60602@beccati.com>
Date: Wed, 26 Jun 2013 18:51:05 +0900
Message-ID: <CAGa2bXYJT+nZFjWht_MpYRitgJ9-N=yVzsJoqax_FVc3pmqqdg@mail.gmail.com>
To: Matteo Beccati <php@beccati.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c3b4aefcd9e604e00b97f2
Subject: Re: [PHP-DEV] pgsql: Binary data support improvement
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a11c3b4aefcd9e604e00b97f2
Content-Type: text/plain; charset=ISO-8859-1

Hi Matteo,

2013/6/26 Matteo Beccati <php@beccati.com>

> I have mixed feelings... I see where this might come in handy, but I
> think it would be a bit too user-unfriendly.
>

I have mixed feelings for supporting direct binary support, too.

Main intension is faster bytea(binary) handling.

Without binary support, client has to encode binary via pg_escape_bytea
and server decode it before saving bytea data. When selecting, server encode
it by using PQescapeByeta algorithm, then client decode it by
pg_unescape_bytea.


> PDO_pgsql on the other hand, when used with explicit parameter binding,
> could automatically use binary format for LOB fields.
>

AFAIK, PDO doesn't handle bytea data natively.

There may be clever usage, but binary support is only for faster bytea
handling.
API isn't great, so if there are objections, I'll spend time rather than
this.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a11c3b4aefcd9e604e00b97f2--