Bruce Momjian wrote:
Agreed that libpqtypes would solve the problem, but the odd thing to me
is that we have gotten very few requests for binary format information
since we added binary prepared parameters years ago, so is no one
actually using it?
I think part of the answer is lack of docume
On Thu, May 8, 2008 at 12:27 PM, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> Andrew Chernow wrote:
> > >>> This is exactly what libpqtypes solves. Not only do we handle
> > >>> formatting of binary formats, we provide a level of protection from
> > >>> internal format changes for libpq users. S
Andrew Chernow wrote:
> >>> This is exactly what libpqtypes solves. Not only do we handle
> >>> formatting of binary formats, we provide a level of protection from
> >>> internal format changes for libpq users. See the example here:
> >>> http://libpqtypes.esilo.com/. So, documentation of binary
Andrew Chernow <[EMAIL PROTECTED]> writes:
> Bruce Momjian wrote:
>> Aleksej Saushev wrote:
>>> "Merlin Moncure" <[EMAIL PROTECTED]> writes:
>>>
Bruce Momjian wrote:
> This brings up a good question. Exactly how do users know what format
> _binary_ is? int4 is network byte order, bu
Bruce Momjian wrote:
Aleksej Saushev wrote:
"Merlin Moncure" <[EMAIL PROTECTED]> writes:
Bruce Momjian wrote:
This brings up a good question. Exactly how do users know what format
_binary_ is? int4 is network byte order, but what about int8, float4,
inet?
This is exactly what libpqtypes so
Aleksej Saushev wrote:
> "Merlin Moncure" <[EMAIL PROTECTED]> writes:
>
> > Bruce Momjian wrote:
> >> This brings up a good question. Exactly how do users know what format
> >> _binary_ is? int4 is network byte order, but what about int8, float4,
> >> inet?
> >
> > This is exactly what libpqtype
