I get bitten by it locally too: if there's a test with an inaccurate sql query with time formatted as string, the sql server doesn't always compute it, because the default "human-readable" time format is taken from the current locale, and to parse it one first has to guess the format itself, which is quite difficult in a heterogeneous system.

DATE '2013-10-12' is the date October 12th to most SQL parsers. Locales and NLS in SQL have bitten me many times until I learned this.

Reply via email to