From: | "Wilhansen Li" <willi(dot)t1(at)gmail(dot)com> |
---|---|
To: | "Richard Huxton" <dev(at)archonet(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: libpq and Binary Data Formats |
Date: | 2007-06-04 17:19:42 |
Message-ID: | bc9549a50706041019t71f8d02ew2c1cc6b8bb28d43e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Basically, better support for binary formats which includes, but not limited
to:
1) functions for converting to and from various datatypes
2) reducing the need to convert to and from network byte order
3) better documentation
My suggestion on using ASN.1 was merely a naive suggestion on how in can be
implemented properly without breaking (future) compatibility because that
seems to be the main problem which prevents the use of binary formats.
On 6/5/07, Richard Huxton <dev(at)archonet(dot)com> wrote:
>
> Wilhansen Li wrote:
> > First of all, apologies if this was not meant to be a feedback/wishlist
> > mailing list.
> >
> > Binary formats in libpq has been (probably) a long
> > issue (refer to the listings below) and I want to express my hope that
> the
> > next revision of PostgreSQL would have better support for binary data
> types
> > in libpq.
>
> Um - speaking as a user, not a developer, I don't actually see a
> description of what problem(s) you are suggesting be solved. Are you
> saying there should be better documentation, or a new format?
>
> --
> Richard Huxton
> Archonet Ltd
>
--
(<_<)(>_>)(>_<)(<.<)(>.>)(>.<)
Life is too short for dial-up.
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-06-04 18:12:54 | Re: recovery_target_xid & crashes on the master |
Previous Message | Kris Jurka | 2007-06-04 17:18:14 | Re: So, why isn't *every* buildfarm member failing ecpg right now? |