| From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Barry Lind" <barry(at)xythos(dot)com> |
| Cc: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "PostgreSQL Development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: OCTET_LENGTH is wrong |
| Date: | 2001-11-19 19:02:11 |
| Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA421280E@m0114.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> What's bothering me right now is the
> difference between client and server encodings. It seems that the
only
> plausible use for octet_length is to do memory allocation on the
client
> side, and for that purpose the length ought to be measured in the
client
> encoding. People seem to be happy with letting octet_length take the
> easy way out (measure in the server encoding), and I'm trying to get
> someone to explain to me why that's the right behavior. I
> don't see it.
I agree. octet_length should be the number of bytes the client gets when
he
does "select textfield from atable".
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-11-19 19:15:11 | Re: OCTET_LENGTH is wrong |
| Previous Message | Peter Eisentraut | 2001-11-19 18:44:30 | Re: postgresql.conf |