It appears that the timestamp I insert and the one I retrieve to and from a MySQL differs (retrieved timestamp is 1 hour after the inserted one). Ignition is running on a docker container created from the original image and mysqlis in another container also from the official image. I'm using zxdbc libs instead of the db modules in ignition but I've set the timezones to Europe/Rome on both containers and on every Ignition setting possible, including Ignition.conf java additional parameters. What is causing the issue? Setting the jdbc connection url parameters to connectionTimeZone=Europe/Rome doesn't seem to help either
I don't see how you can expect to be supported when doing this. (If you are using Ignition Edge, you are violating the license.)
I'm not, I just don't like using the integrated module for querys
Are you using a timezone-aware column type in the DB? (MySQL datetime columns are not, timestamp columns are, but have side effects.)
1 Like
It is mysql time, so using datetime instead might be the solution?
No, timestamp is the column type that usually behaves correctly. But definitely examine all of your time zone expectations on both systems.
1 Like
okay I was actually using mysql "time", and even changing to timestamp or datetime has no effect, that's kind of confusing