Re: getXXX methods
| От | Oliver Jowett |
|---|---|
| Тема | Re: getXXX methods |
| Дата | |
| Msg-id | 40EB385F.9030704@opencloud.com обсуждение исходный текст |
| Ответ на | Re: getXXX methods (Dave Cramer <pg@fastcrypt.com>) |
| Ответы |
Re: getXXX methods
|
| Список | pgsql-jdbc |
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
В списке pgsql-jdbc по дате отправления: