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

cleanup exception handling - use new exception hierarchy (since python 2.5)

2014-10-02T20:00:31+00:00

improve exception vs. exit handling

2014-09-23T21:28:11+00:00

- Fixed the version string detection in the pymssql dialect to

2014-09-16T21:40:06+00:00

work with Microsoft SQL Azure, which changes the word "SQL Server"
to "SQL Azure".
fixes #3151

- ensure literal_binds works with LIMIT clause, FOR UPDATE

2014-09-03T23:42:38+00:00

- The hostname-based connection format for SQL Server when using

2014-09-03T14:31:29+00:00

pyodbc will no longer specify a default "driver name", and a warning
is emitted if this is missing.  The optimal driver name for SQL Server
changes frequently and is per-platform, so hostname based connections
need to specify this. DSN-based connections are preferred.
fixes #3182

- update some SQL server tests, support

2014-07-22T17:42:38+00:00

- add support for IDENTITY INSERT setting for INSERT with inline VALUES

- apply pep8 formatting to sqlalchemy/sql, sqlalchemy/util, sqlalchemy/dialects,

2014-07-20T16:44:40+00:00

sqlalchemy/orm, sqlalchemy/event, sqlalchemy/testing

- Fixed a regression from 0.9.5 caused by :ticket:`3025` where the

2014-07-14T23:16:11+00:00

query used to determine "default schema" is invalid in SQL Server 2000.
For SQL Server 2000 we go back to defaulting to the "schema name"
parameter of the dialect, which is configurable but defaults
to 'dbo'. fixes #3025

- Added statement encoding to the "SET IDENTITY_INSERT"

2014-07-14T23:02:20+00:00

statements which operate when an explicit INSERT is being
interjected into an IDENTITY column, to support non-ascii table
identifiers on drivers such as pyodbc + unix + py2k that don't
support unicode statements.
ref #3091 as this fix is also in that issue's patch, but is
a different issue.

- In the SQL Server pyodbc dialect, repaired the implementation

2014-07-14T22:54:23+00:00

for the ``description_encoding`` dialect parameter, which when
not explicitly set was preventing  cursor.description from
being parsed correctly in the case of result sets that
contained names in alternate encodings.  This parameter
shouldn't be needed going forward.
fixes #3091