Re: Bug : FAST_NUMBER_FAILED when getting NaN on BigDecimal
| От | Mikko Tiihonen |
|---|---|
| Тема | Re: Bug : FAST_NUMBER_FAILED when getting NaN on BigDecimal |
| Дата | |
| Msg-id | 504F771B.2000909@nitorcreations.com обсуждение исходный текст |
| Ответ на | Bug : FAST_NUMBER_FAILED when getting NaN on BigDecimal (DocSea - Patrice Delorme <pdelorme@docsea.com>) |
| Список | pgsql-jdbc |
On 09/11/2012 01:37 PM, DocSea - Patrice Delorme wrote: > Hi, > > It is impossible to fetch data when numeric value in database is NaN > It throws FAST_NUMBER_FAILED (postgresql-jdbc-9.1-902:AbstractJdbc2ResultSet:2176) because my value is not numeric (NaN). > This is incorect behaviour since 'NaN' is a legal value in postgres for numeric type. > > problem is in postgresql-jdbc-9.1-902.jdbc4 > but it seems areound for ages... since I discovered it first in postgresql-8.3-603.jdbc3... Can you provide a more concrete example code to show when the FAST_NUMBER_FAILED exception is seen by jdbc using application. I did a quick look at the code and the exception in question looks like just a jdbc driver internal way to switch to slowerparsing of input values when fast parsing fails. It should never escape to applications. -Mikko
В списке pgsql-jdbc по дате отправления: