| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "Dawid Kuroczko" <qnex42(at)gmail(dot)com>, "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: RFD: hexstring(n) data type |
| Date: | 2008-04-18 00:21:33 |
| Message-ID: | 2352.1208478093@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> However bytea has an inconvenient string representation. Really I would prefer
> if bytea were *always* read and written in hex format.
Yeah, the escaping rule is a mess: hard to work with and even less
storage-efficient than hex would be.
> We could have a guc to
> enable this but it would make it hard to write code which would function
> consistently as part of a larger application.
Well, the datetime types have had DateStyle for years and people have
managed to deal with it, so maybe you're overestimating the problem.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-04-18 00:23:58 | Re: pgsql: Fix a couple of oversights associated with the "physical tlist" |
| Previous Message | Gregory Stark | 2008-04-18 00:14:30 | Re: pgsql: Fix a couple of oversights associated with the "physical tlist" |