On 2017/05/22 3:57 PM, Silvio wrote:

Thanks for the reply. I was expecting something like that but how do I discover 
what the offending data is? What type of
column could cause this? And what values should I look for?

It's a TIMESTAMP or TIMESTAMP WITH TIME ZONE column.

Specifically, it's the time/day portion which is a 24-hour time value specified 
in nanoseconds.

The exception means that the value is either < 0 or greater than "24 hours in 
nanoseconds"

There is no lenient mode (short of modifying the source code yourself, which is 
quite possible)

You'd need to view things in a debugger to see which exact row it is.
Or select a row at a time from your table until you hit the dodgy row.

--
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.

Reply via email to