delta/python-packages/sqlalchemy.git/lib/sqlalchemy/connectors, branch pr/312 github.com: zzzeek/sqlalchemy.git Use SQL Server SERVERPROPERTY for version info w/ pyodbc 2016-10-04T15:17:26+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-10-04T15:17:26+00:00 f0ea9e37f94bd39fa4f0785dbdcd0ee1759c4a11 Updated the server version info scheme for pyodbc to use SQL Server SERVERPROPERTY(), rather than relying upon pyodbc.SQL_DBMS_VER, which continues to be unreliable particularly with FreeTDS. Change-Id: I4ff49ae13c8ff51bd764980131d41c18d73d87ce Fixes: #3814 
Updated the server version info scheme for pyodbc to use SQL Server
SERVERPROPERTY(), rather than relying upon pyodbc.SQL_DBMS_VER, which
continues to be unreliable particularly with FreeTDS.

Change-Id: I4ff49ae13c8ff51bd764980131d41c18d73d87ce
Fixes: #3814
Spelling fixes: "an SQL" -> "a SQL", see #266 2016-05-05T06:02:38+00:00 Ville Skyttä ville.skytta@iki.fi 2016-05-05T06:02:07+00:00 61f9e3761245a55f8997ec40b6983bb0770fdec4 






- happy new year
2016-01-29T16:20:22+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2016-01-29T16:20:22+00:00

859379e2fcc4506d036700ba1eca4c0ae526a8ee












- copyright 2015
2015-03-10T19:24:28+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2015-03-10T19:24:28+00:00

50866d2f857dd45bb2d186a0fa076768437d62a3












- The hostname-based connection format for SQL Server when using
2014-09-03T14:31:29+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2014-09-03T14:30:51+00:00

4399431b53e5d132672431205c654d7d6b32dd77

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





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







- Added statement encoding to the "SET IDENTITY_INSERT"
2014-07-14T23:02:20+00:00

Mike Bayer
mike_mp@zzzcomputing.com

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

2825730e7be6e18aac32bcef4f6eeb0a5acab2a0

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.





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.







PEP8 style fixes
2014-07-14T00:10:55+00:00

Brian Jarrett
celttechie@gmail.com

2014-07-10T22:28:49+00:00

28dd15081db4b7e978fa7a187c3aef1c0e4ad4e3












- break up the <authors> copyright comment as part of a pass
2014-07-09T22:26:55+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2014-07-09T22:26:55+00:00

5407ec9d389cfa1cdd4ed4b82ba311085132d9db

to get all flake8 passing





to get all flake8 passing







- remove drizzle dialect
2014-05-30T22:06:09+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2014-05-30T22:06:09+00:00

809a7890a1cc1c957ae2263bdcbda2d42f5372ba

- restore mysqldb fully within dialects/mysql/, it's no longer a connector.
fixes #2984





- restore mysqldb fully within dialects/mysql/, it's no longer a connector.
fixes #2984







- Fixed bug which prevented MySQLdb-based dialects (e.g.
2014-02-03T17:04:51+00:00

Mike Bayer
mike_mp@zzzcomputing.com

2014-02-03T17:04:51+00:00

8b08b1a35b85c24349226c34e6834f4f60db3c6f

pymysql) from working in Py3K, where a check for "connection
charset" would fail due to Py3K's more strict value comparison
rules.  The call in question  wasn't taking the database
version into account in any case as the server version was
still None at that point, so the method overall has been
simplified to rely upon connection.character_set_name().
[ticket:2933]





pymysql) from working in Py3K, where a check for "connection
charset" would fail due to Py3K's more strict value comparison
rules.  The call in question  wasn't taking the database
version into account in any case as the server version was
still None at that point, so the method overall has been
simplified to rely upon connection.character_set_name().
[ticket:2933]