| From: | Thomas Hallgren <thhal(at)mailblocks(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Binary Cursors, and the COPY command |
| Date: | 2004-07-27 06:39:49 |
| Message-ID: | ce4t7l$pas$2@sea.gmane.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
Oliver Jowett wrote:
> This is not true if you happen to be using Java on the client side,
> which has no idea (unless you grot around in the guts of the JVM) what
> the native byte order is.
>
The method java.nio.ByteOrder.nativeOrder() will tell you what the
native byte order is.
> This actually means that Java clients have the
> opposite problem -- it's a lot of work to try to use the 7.3-style
> binary formats.
>
The commonly used java.io.DataInput will always use network order but
it's easy enough to read/write little endian using the java.nio and
java.nio.channel packages.
Regards,
Thomas Hallgren
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2004-07-27 07:07:47 | Re: Binary Cursors, and the COPY command |
| Previous Message | Kris Jurka | 2004-07-27 06:16:47 | casting strings to multidimensional arrays yields strange results |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2004-07-27 07:07:47 | Re: Binary Cursors, and the COPY command |
| Previous Message | Kris Jurka | 2004-07-27 05:20:49 | Re: patch: ensure testdbencoding test table is dropped |