delta/python-packages/sqlalchemy.git/test/dialect/mssql, branch oracle_numeric github.com: zzzeek/sqlalchemy.git Add SQL Server CI coverage 2017-08-31T21:20:26+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-08-29T16:36:54+00:00 2efd89d02941ab4267d6e2842963fd38b1539f6c Change-Id: Ida0d01ae9bcc0573b86e24fddea620a38c962822 
Change-Id: Ida0d01ae9bcc0573b86e24fddea620a38c962822
Add placeholder XML support 2017-05-26T15:24:25+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-05-26T15:24:25+00:00 b1369b47217558779a5b8a17ecd945cedd608dc7 Added a placeholder type :class:`.mssql.XML` to the SQL Server dialect, so that a reflected table which includes this type can be re-rendered as a CREATE TABLE. The type has no special round-trip behavior nor does it currently support additional qualifying arguments. Change-Id: I651fa729bd8e9b31a0b5effe0839aff077d77c46 Fixes: #3973 
Added a placeholder type :class:`.mssql.XML` to the SQL Server
dialect, so that a reflected table which includes this type can
be re-rendered as a CREATE TABLE.  The type has no special round-trip
behavior nor does it currently support additional qualifying
arguments.

Change-Id: I651fa729bd8e9b31a0b5effe0839aff077d77c46
Fixes: #3973
Recognize brackets, quoted_name in SQL Server schema 2017-04-04T17:45:06+00:00 Mike Bayer mike_mp@zzzcomputing.com 2017-04-03T19:05:27+00:00 9f82afea25958910038ec768d81b157d9d2fdc7c The SQL Server dialect now allows for a database and/or owner name with a dot inside of it, using brackets explicitly in the string around the owner and optionally the database name as well. In addition, sending the :class:`.quoted_name` construct for the schema name will not split on the dot and will deliver the full string as the "owner". :class:`.quoted_name` is also now available from the ``sqlalchemy.sql`` import space. Change-Id: I77491d63ce47638bd23787d903ccde2f35a9d43d Fixes: #2626 
The SQL Server dialect now allows for a database and/or owner name
with a dot inside of it, using brackets explicitly in the string around
the owner and optionally the database name as well.  In addition,
sending the :class:`.quoted_name` construct for the schema name will
not split on the dot and will deliver the full string as the "owner".
:class:`.quoted_name` is also now available from the ``sqlalchemy.sql``
import space.

Change-Id: I77491d63ce47638bd23787d903ccde2f35a9d43d
Fixes: #2626
Make all tests to be PEP8 compliant 2017-02-07T16:21:56+00:00 Khairi Hafsham jumanjisama@gmail.com 2017-02-02T18:02:21+00:00 772374735da27df1ddb907f4a0f5085b46dbe82b tested using pycodestyle version 2.2.0 Fixes: #3885 Change-Id: I5df43adc3aefe318f9eeab72a078247a548ec566 Pull-request: https://github.com/zzzeek/sqlalchemy/pull/343 
tested using pycodestyle version 2.2.0

Fixes: #3885
Change-Id: I5df43adc3aefe318f9eeab72a078247a548ec566
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/343
Quote URL tokens with semicolons for pyodbc, adodbapi 2016-11-11T18:30:25+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-11-10T22:08:06+00:00 5fba7db9be7a03076d50051fb84dade31d55262e Fixed bug in pyodbc dialect (as well as in the mostly non-working adodbapi dialect) whereby a semicolon present in the password or username fields could be interpreted as a separator for another token; the values are now quoted when semicolons are present. Change-Id: I5f99fd8db53ebf8e805e7d9d60bc09b8f1af603f Fixes: #3762 
Fixed bug in pyodbc dialect (as well as in the mostly non-working
adodbapi dialect) whereby a semicolon present in the password
or username fields could be interpreted as a separator for another
token; the values are now quoted when semicolons are present.

Change-Id: I5f99fd8db53ebf8e805e7d9d60bc09b8f1af603f
Fixes: #3762
Deprecate FromClause.count() 2016-06-14T15:48:04+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-06-13T19:18:13+00:00 f38f890849700ee1bf719a31275260e2da455bc3 count() here is misleading in that it not only counts from an arbitrary column in the table, it also does not make accommodations for DISTINCT, JOIN, etc. as the ORM-level function does. Core should not be attempting to provide a function like this. Change-Id: I9916fc51ef744389a92c54660ab08e9695b8afc2 Fixes: #3724 
count() here is misleading in that it not only
counts from an arbitrary column in the table, it also
does not make accommodations for DISTINCT, JOIN, etc.
as the ORM-level function does.  Core should not be
attempting to provide a function like this.

Change-Id: I9916fc51ef744389a92c54660ab08e9695b8afc2
Fixes: #3724
Allow creating explicit non-clustered keys and indexes MS SQL. 2016-06-06T18:27:31+00:00 Saulius Žemaitaitis saulius@zemaitaitis.lt 2016-04-12T03:16:45+00:00 a5f92314edd45a2e411b0f5b3c4d4bec0c7d92f8 mssql_clustered=False on Index, UniqueConstraint, PrimaryKeyConstraint now renders NONCLUSTERED. The default of mssql_clustered is now None. Co-Authored-By: mike bayer <mike_mp@zzzcomputing.com> Change-Id: Id6b8d840e355be8f8fa72360cb4b6d2617ba72cf Pull-request: https://github.com/zzzeek/sqlalchemy/pull/252 
mssql_clustered=False on Index, UniqueConstraint,
PrimaryKeyConstraint now renders NONCLUSTERED.
The default of mssql_clustered is now None.

Co-Authored-By: mike bayer <mike_mp@zzzcomputing.com>
Change-Id: Id6b8d840e355be8f8fa72360cb4b6d2617ba72cf
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/252
Use new mxODBC 3.3.4 varbinary null symbol 2016-05-31T15:03:34+00:00 Sheila Allen sallen@zeomega.com 2016-04-11T19:29:03+00:00 3f55039e7f15efafacc3e8e0fbf0ba38fa612b09 Use new mxODBC 3.3.4 varbinary null symbol with VARBINARY data types when value is None(based on similar change to pyodbc). Fix a test to pass on mxODBC starting w 3.3.3 version Change-Id: Id703ecb51ebc5db149c81fef124f673433606c7f Pull-request: https://bitbucket.org/zzzeek/sqlalchemy/pull-requests/58 
Use new mxODBC 3.3.4 varbinary null symbol with VARBINARY
data types when value is None(based on similar change to pyodbc).
Fix a test to pass on mxODBC starting w 3.3.3 version

Change-Id: Id703ecb51ebc5db149c81fef124f673433606c7f
Pull-request: https://bitbucket.org/zzzeek/sqlalchemy/pull-requests/58
Fix label referencing in SQL Server OFFSET logic 2016-05-10T16:55:23+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-05-10T16:49:56+00:00 0604116814a862d4d9dbc1a8866a2a3b0126caf1 Fixed bug where by ROW_NUMBER OVER clause applied for OFFSET selects in SQL Server would inappropriately substitute a plain column from the local statement that overlaps with a label name used by the ORDER BY criteria of the statement. Change-Id: Ic2500c886cbfc83a1ad5a2681783f008b9f23838 Fixes: #3711 
Fixed bug where by ROW_NUMBER OVER clause applied for OFFSET
selects in SQL Server would inappropriately substitute a plain column
from the local statement that overlaps with a label name used by
the ORDER BY criteria of the statement.

Change-Id: Ic2500c886cbfc83a1ad5a2681783f008b9f23838
Fixes: #3711
- update the mssql autoincrement reflection test to accommodate 2016-02-21T01:43:36+00:00 Mike Bayer mike_mp@zzzcomputing.com 2016-02-21T01:43:36+00:00 6713817e1186cd1e36c9aea9d89a30bc299ffe27 the new behavior of the autoincrement flag as per ref #3216 
the new behavior of the autoincrement flag as per ref #3216