| From: | Rod Taylor <pg(at)rbt(dot)ca> |
|---|---|
| To: | "Eugene E(dot)" <sad(at)bankir(dot)ru> |
| Cc: | PFC <lists(at)peufeu(dot)com>, Achilleus Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: have you feel anything when you read this ? |
| Date: | 2006-03-20 15:58:08 |
| Message-ID: | 1142870288.35058.29.camel@home |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
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.
--
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2006-03-20 16:10:30 | Re: have you feel anything when you read this ? |
| Previous Message | Fay Du | 2006-03-20 15:23:27 | pgsql2shp - Could not create dbf file |