| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | Kris Jurka <books(at)ejurka(dot)com>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: getXXX methods |
| Date: | 2004-07-07 01:01:35 |
| Message-ID: | 1089162095.1508.173.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Oliver,
Well as Kris pointed out the javadoc is next to useless here. I see no
harm in truncating the data, my assumption being that the user knows
what they are doing.
Dave
On Tue, 2004-07-06 at 19:40, Oliver Jowett wrote:
> Dave Cramer wrote:
> > I was thinking that parsing the double would be less efficient than
> > Byte.parseByte().
> >
> > The spec suggests that the user would know what they are doing calling
> > getByte on a double column.
>
> Yeah, specifically table B-6 says you can use getByte() on pretty much
> any numeric SQL type, and (bizarrely) on varchar, char, longvarchar, and
> boolean types too.
>
> The spec & javadoc for java.sql.DataTruncation implies we should
> generate DataTruncation as a warning if we truncate data on read. I
> suppose that loss of precision counts as truncation?
>
> -O
>
>
>
> !DSPAM:40eb3871277871679725527!
>
>
--
Dave Cramer
519 939 0336
ICQ # 14675561
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2004-07-07 01:10:29 | Re: getXXX methods |
| Previous Message | Oliver Jowett | 2004-07-06 23:40:15 | Re: getXXX methods |