ok, so 22 solved the issue for me now
# adobe
l
ok, so 22 solved the issue for me now
s
Just so folks are aware, who might not have read the MySQL JDBC driver release notes in depth, there was a big change in the 8.0.23 driver compared to the 8.0.22 driver in the area of date/time fields. In theory, it's a bug fix but the reality is that a lot of code depended on the bug so this patch-level release is a breaking change for a lot of people. We're stuck on 8.0.22 at work, completely unrelated to CFML, because we haven't had the time/energy to dig into our codebase and make the changes necessary for this! See https://dev.mysql.com/doc/relnotes/connector-j/8.0/en/news-8-0-23.html#connector-j-8-0-23-feature for more details. They changed the default behavior for timezones and you need to add a new connection parameter but they also changed the return value for
getObject()
that requires code changes!
👍 1
e
Always applicable to semantic version conversations: https://xkcd.com/1172/
😜 2
l
Gotta love breaking changes in patch releases...
s
I have to say, it's one thing I really like about the Clojure community: they value backward compatibility to the point that instead of introducing breaking changes, they will add a new function or package with the modified behavior, allowing users to adopt the changes as and when they want while still guaranteeing existing code continues to run (and libraries tend to be very small and focused in their functionality so keeping that "legacy" code around has very little cost). There is a lot of Clojure code out there written against, say, version 1.3.0 from a decade ago that still runs unchanged on 1.11.1 (the latest stable version) -- and can usually have all its 3rd party (Clojure) libraries safely updated too...