Anyone else run into this? Can someone explain what causes this?
We have a trigger that sets a table column to a date when it fires. The column has a DATE datatype. The only way anything gets into that column is via the trigger. The column gets set to SYSDATE. The problem is the date inserted into the table is invalid! It falls in that "twilight zone" between 2am and 3am on the day where we switch over to daylight savings time. For example one value is "09-Mar-2014 02:05:01". In theory that time never existed in the local time zone.
How is this happening and how do I prevent it?