New job, new database, new annoyances to get over. Same ol' same ol'.
- Default datetime format not ISO format.
- Datetime to char conversion function doesn't have ISO as a choice (but lots of others)
- Table and column names are case sensitive ("select foo" ne "select FOO").
- ODBC driver prepares statements, but barfs after executing a few times.
Updating the ODBC driver might fix the problem (Data type for parameter x has changed since first SQLExecute call), but it's a commercial driver, I don't have admin rights on my pc, and I'd have to get the planets aligned first.
And, writing an "iso_format(datetime)" stored procedure might be a good idea, but there's plenty of code already that depends on the current date format.
Case
jplindstrom on 2007-03-09T11:52:12
The case sensitivity on table names is actually dependent on how the charachter set of the dataserver is configured (i.e. whether comparisons with data in tables is case sensitive or not). That configuration applies to the repository tables (which store the user table names) as well.
