delta/python-packages/sqlalchemy.git/lib/sqlalchemy/dialects/mssql, branch pr/9

When querying the information schema on SQL Server 2000, removed

2013-06-06T16:52:18+00:00

a CAST call that was added in 0.8.1 to help with driver issues,
which apparently is not compatible on 2000.
The CAST remains in place for SQL Server 2005 and greater.
[ticket:2747]

- some tweaks to try to help out mssql+pyodbc support a bit, py3k is really

2013-06-03T16:54:56+00:00

not happening too well (I need to stick with linux + freetds 0.91, I know)

merge default

2013-05-15T19:47:11+00:00

Regression from this ticket caused the unsupported keyword

2013-05-15T19:46:29+00:00

"true" to render, added logic to convert this to 1/0
for SQL server.
[ticket:2682]

plugging away

2013-04-28T00:38:53+00:00

work through dialects

2013-04-28T00:02:24+00:00

- the raw 2to3 run

2013-04-27T23:53:57+00:00

- went through examples/ and cleaned out excess list() calls

- this pymssql test needs to be against the pymssql dialect

2013-04-18T21:41:30+00:00

- Part of a longer series of fixes needed for pyodbc+
      mssql, a CAST to NVARCHAR(max) has been added to the bound
      parameter for the table name and schema name in all information schema
      queries to avoid the issue of comparing NVARCHAR to NTEXT,
      which seems to be rejected by the ODBC driver in some cases,
      such as FreeTDS (0.91 only?) plus unicode bound parameters being passed.
      The issue seems to be specific to the SQL Server information
      schema tables and the workaround is harmless for those cases
      where the problem doesn't exist in the first place.
[ticket:2355]

Merged in sontek/sqlalchemy/add_better_disconnect_checks (pull request #47)

2013-03-29T16:03:17+00:00

Add disconnect check on timeouts

cleaned up errors, only check for connection timeout for now

2013-03-18T22:04:30+00:00