From: | Theo Kramer <theo(at)flame(dot)co(dot)za> |
---|---|
To: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Binary cursors, numerics and other types |
Date: | 1999-08-16 18:22:44 |
Message-ID: | 37B856F4.190B2F37@flame.co.za |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> It is not libpq's job to try to deal with binary data from the server
> --- for one thing, libpq may be compiled on a different architecture
> with a different representation than the server is (wrong endianness,
> different floating point format, etc). libpq doesn't even have any
> way of finding out whether a conversion is needed, let alone doing it.
>
> In the current scheme of things, binary cursors are of very limited use,
> and you are *really* foolish if you try to use them for anything except
> the most primitive data types like "int4". Your code will break without
> warning whenever Jan feels like changing the internal representation of
> numeric, as I believe he intends to do soon. We have never guaranteed
> that the internal representation of date/time types is frozen, either
> --- Thomas has been heard muttering about replacing timestamp with
> datetime, for example.
Hmm, a real pity. Always thought that it was the responsibility of the
persistant store to provide a heterogenous interface. Oh well back
to messy error prone conversions to and from strings.
--------
Regards
Theo
From | Date | Subject | |
---|---|---|---|
Next Message | Ross J. Reedstrom | 1999-08-16 18:29:52 | Re: [HACKERS] Long table names |
Previous Message | Bruce Momjian | 1999-08-16 18:01:42 | Re: [HACKERS] Long table names |