Failed SQL queries

There was a need in updating a big data set stored in Oracle database. Currently existing solution for this purpose was implemented as myBatis script. It contained resetting timestamps in form - '01-JAN-1970' . Execution of this script was constantly failing on environments with Czech localization. This was caused by DBMS installation creating a timestamp in a form - '01-LED-1970' , so the month was not recognized.
Submitted by Oleksandr Korobeinykov on Sun, 12/04/2016 - 11:00
1 answer

Solution for "Failed SQL queries"

Solution: as no unified timestamp format was used in production - it was decided to use only English environments from no on.
To prevent such things in future it was decided to always use to_timestamp functions and try to avoid localization specific notations.

Submitted by Oleksandr Korobeinykov on Mon, 12/05/2016 - 19:35

Taggings: