| From: | James Robinson <jlrobins(at)socialserve(dot)com> |
|---|---|
| To: | Paul Thomas <paul(at)tmsl(dot)demon(dot)co(dot)uk> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: JBoss w/int8 primary keys in postgres ... |
| Date: | 2003-09-07 19:09:23 |
| Message-ID: | CA913180-E166-11D7-9C55-000A9566A412@socialserve.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Sunday, September 7, 2003, at 06:44 AM, Paul Thomas wrote:
> It would need to settable in the url string to be used in an EJB
> container.
>
> Comments?
Well, reading the associated threads more closely, I see that Tom
announced that there was a proposed fix in the backend for 7.4 (see
http://archives.postgresql.org/pgsql-jdbc/2002-10/msg00164.php). I'm
cooking 7.4B2 right now to see if anything is indeed different. But,
given the most recent discussion in performance-land, dated this past
Friday, I'm not expecting too much.
A backend fix would be the clearest answer, since the principle of
least surprise is being violated by the backend, not the JDBC driver.
I'm just not sure if that is/will be done in a timely enough fashon,
given I have this problem *now*, and our particular frontend-of-choice
can indeed inject a lossless cast in the setLong() path (and, likewise,
perhaps a '::int2' for the setShort() path as well).
CMP will be the death of us all.
James
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Stephenson | 2003-09-08 09:10:03 | Re: expression IN value list |
| Previous Message | Paul Thomas | 2003-09-07 10:44:02 | Re: JBoss w/int8 primary keys in postgres ... |