Explain why datetime types for @Version get OLE using >= Java 15

Thanks, appreciate the response. I’ve seen the resolved JIRA that is available in version 6 (and we plan on upgrading soon).

But for now, the reason I posted this query to the forum is to better understand why the precision is required.

In one case, our web app uses MySQL which restricts datetime precision to 6, and despite the OS and JDK allowing for nanosecond precision, it doesn’t seem to be a problem.
But as soon as we point that web app to H2 (which supports up to precision 9) I see the OLE.

So am hoping to understand what is the code mechanism that causes this issue.