databaseZone, javaZone not honored in 3.2.0.GA about jadira HOT 11 CLOSED

Did you solved this problem?

from jadira.

Try 5.1.5 driver (its a typo). Also can you try jadira 3.1.0-CR8. Would like to know how this works for you (as I may reintroduce the behaviours from that version).

from jadira.

We're also facing those problems. And yes, in jadira-3.1.0-CR8 javaZone and databaseZone were respected. (Though it had this #5 DST problem, which renders it unusable for us.)

from jadira.

There is not a good solution due to the flaws of JDBC, but I can give the option to configure which of the two behaviours to use which is what I am thinking currently. Open to user suggestions on this.

from jadira.

I agree: when in doubt, it would be nice to be able to decide which is the lesser evil.

from jadira.

Also the handling with either method is not consistent across databases or even revisions of databases. Its a torrid mess when it comes to timezones and JDBC

from jadira.

Should just mention about the useLegacyDatetimeCode=false connection parameter. See the answer to this question https://stackoverflow.com/questions/7605953/how-to-change-mysql-timezone-in-java-connection

from jadira.

This isn't fixed in 4.0.0.GA, is it?

from jadira.

With MySQL it is recommended to pass the connection parameters "zeroDateTimeBehavior=convertToNull&useLegacyDatetimeCode=false". Can you confirm you are using these. Have you been using these parameters?

from jadira.

Closing this due to inactivity - I assume my last commit addressed the issue

from jadira.

Hey @chrisphe, using the given connection parameters indeed solved our problem. Sorry for not reporting back, and thank you for your support here!

from jadira.