Hi,
I recently helped one of our users with a MySQL timezone issue, and I
realized that the default legacy timezone handling is to be avoided.
Basically, you want to set this "useLegacyDatetimeCode' configuration
property to false.
for more details, check out this article:
https://vladmihalcea.
Hi Vikas,
is it possible you're using ScrollableResults and your own application
is not making sure to close them all?
sorry for asking the obvious, but you know sometimes it helps ;)
Thanks,
Sanne
On 15 March 2017 at 06:55, Vlad Mihalcea wrote:
> Hi,
>
> You should replicate this behavior us
I'm not sure exactly where the fault lies (java.util versus java.sql), but
we should certainly help hide that if we reasonably can. But conceptually,
milliseconds on a DATE (no time) makes zero sense at all. So where does
the milliseconds come from?
It is also possible that the db is (incorrectl
Hi Christian,
More comments below...
On Fri, Mar 3, 2017 at 4:38 PM, Christian Beikov wrote:
> Thanks for the comments, I have updated the PR.
>
> I think that it is important to have a complete fix and I am already
> working on that, but this issue was specifically about the L2 cache, so I
> w
