From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
---|---|
To: | Thomas Hallgren <thhal(at)mailblocks(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Binary Cursors, and the COPY command |
Date: | 2004-07-27 10:10:57 |
Message-ID: | 41062A31.7000800@opencloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
Thomas Hallgren wrote:
> "Oliver Jowett" <oliver(at)opencloud(dot)com> wrote in message
> news:4105FF43(dot)40508(at)opencloud(dot)com(dot)(dot)(dot)
>
>>NIO is not present before JDK 1.4. The JDBC driver, at least, needs to
>>support earlier JVMs.
>>
>
> Clients only capable of network order (such as a Java 1.3 based JDBC driver)
> must of course be supported still. No argument there. My objection was to
> your general statement that "Java has no idea what the native byte order
> is".
I suppose so. I'd point out that the NIO byteorder info is really just
an optimization hint -- the rest of the NIO API is byteorder agnostic,
regardless of what the native byteorder is.
>>The problem with using native byte orderings is not the byte ordering
>>itself, but that the order is unpredictable -- at best, you have to
>>implement code to handle both orders, and at worst you have to just take
>>a guess and hope you were right..
>
> Sure, but those problems are present regardless of implementation language.
That was my real argument..
-O
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Hallgren | 2004-07-27 10:41:49 | Re: Binary Cursors, and the COPY command |
Previous Message | Oliver Jowett | 2004-07-27 10:04:41 | Re: [HACKERS] Binary Cursors, and the COPY command |
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Hallgren | 2004-07-27 10:41:49 | Re: Binary Cursors, and the COPY command |
Previous Message | Oliver Jowett | 2004-07-27 10:04:41 | Re: [HACKERS] Binary Cursors, and the COPY command |