Timestamps have always been a bit of a pain since JDBC does not support both with and without timezones. It really only supports timestamps with timezone.
We have made decisions in the driver which are not optimal for everyone. The reason it does this is for binary transfers of data. We need to control which timezone both the server and the client are operating in.
Yes, that is where we think we are heading, the issue is that the code does not know what it needs to be set back to. We have 90 databases with 5 different time zones. I was just hoping for a more elegant solution than writing a lookup table that says if you are connecting to db x then set to timezone y.
Anyone have a suggestion for setting the timezone back to the Postgres db default on a connection. JDBC now sets the timezone to be the client which is my web server and ignores the default timezone that I have set in the DB. There are large parts of my code that I have never worried about timezones because the DB would handle it. Before I head down that path, I thought I would check and see if there was an easier way for me to put it back into the database.
My latest issue is I create a date object and set it to 3am PST, If I save it into a timestamp with timezone the db saves it at 3am PST when I pull it out. If I save it to timestamp without timezone, I get 6am now where as before I would get 3am.
