From: Rod Taylor <pg@rbt.ca>
To: Eugene E. <sad@bankir.ru>
Cc: PFC <lists@peufeu.com>
Cc: Achilleus Mantzios <achill@matrix.gatewaynet.com>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: have you feel anything when you read this ?
Date: Mon, 20 Mar 2006 10:58:08 -0500
Message-ID: <1142870288.35058.29.camel@home> (raw)
In-Reply-To: <441EC1CC.4070300@bankir.ru>
References: <Pine.LNX.4.44.0603201522410.22894-100000@matrix.gatewaynet.com>
<441EA0A7.8030601@bankir.ru>
<op.s6pt28eacigqcu@apollo13>
<441EC1CC.4070300@bankir.ru>
On Mon, 2006-03-20 at 17:53 +0300, Eugene E. wrote:
> I wrote:
>
> >> the problem is: you'll get this four byte sequence '\000' _instead_
> >> of NUL-byte anyway.
>
> You wrote:
>
> > Your client library should take care of escaping and de-escaping.
>
> We both agree as you see.
>
> Then i am asking:
> WHY should a client take care of de-escaping ? Why not to get his data
> unchanged ?
Request the data be delivered to you in binary format instead of text
format (see PQexecParams, PQexecPrepared, etc).
When you request text format it requires some escaping to occur for
obvious reasons, but you don't need to worry about the length of the
data.
When you request binary escaping is not required but you do need to
worry about the length of the data.
Pick the method that suits you best.
--
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: pg@rbt.ca, sad@bankir.ru, lists@peufeu.com, achill@matrix.gatewaynet.com, peter_e@gmx.net
Subject: Re: have you feel anything when you read this ?
In-Reply-To: <1142870288.35058.29.camel@home>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox