From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
Cc: | "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: getXXX methods |
Date: | 2004-07-06 18:46:07 |
Message-ID: | Pine.BSO.4.56.0407061336560.12042@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Fri, 2 Jul 2004, Dave Cramer wrote:
> There is a table in the jdbc spec which suggests that
> there is a preferred method for getting the column information, and at
> non-preferred method.
>
> would all the numeric values be truncated ?
>
> What do we do with char, varchar, longvarchar ?
It's tough to say. Looking at the current situation for retrieving double
values with getInt() the current driver will throw an Exception on a out
of range value because it starts with a String and uses Integer.parseInt()
on it. Contrast this with the result of
Double d = new Double(Double.MAX_VALUE);
System.out.println(d.intValue());
which truncates the double to Integer.MAX_VALUE. The javadocs are
useless, but I prefer the Exception to silent truncation, so I would
suggest getByte can be used on any integer value of -128 to 127 regardless
of its storage form (like text). The question of comparing floating point
numbers should be the same, but we may run into problems when 1 is
represented as 1.00000001.
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2004-07-06 20:23:07 | Re: getXXX methods |
Previous Message | Ralph | 2004-07-06 10:26:52 | no link in GBorg |