Hi folks,

It appears as though if I tweak the StatementType from 
StatementType.PREPARED_STATEMENT to StatementType.STATIC_STATEMENT
that my NaN is preserved.  I need to investigate more as to why, but this 
looks promising.  Any opinions or experience, is still more than 
appreciated.

Thanks all,
-Charlie

On Friday, April 6, 2018 at 11:18:39 AM UTC-7, Charles Henry wrote:
>
> Hi folks,
>
> I realize that one of the purposes of JOOQ is to ensure safe datatype 
> conversions, and this question may be flying in the face of the purpose of 
> JOOQ.
>
> I see that deep under the hood, say when communicating with Amazon 
> Redshift, a BigInt or INT8 is treated as a Double, and if passed a "NaN" 
> the value passed is treated as Double.NaN, which gets casted around and 
> passed into Long.valueOf, which safely converts my NaN to a 0.
>
> I see no API hooks to disable this conversion.  Is there anything I can do 
> to force JOOQ to keep the NaN regardless of datatype and SQL dialect?
>
> Thanks folks,
> -Charlie
>

-- 
You received this message because you are subscribed to the Google Groups "jOOQ 
User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jooq-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to