delta/python-packages/sqlalchemy.git/test/dialect/mssql, branch pr_github_284

Allow creating explicit non-clustered keys and indexes MS SQL.

2016-06-06T18:27:31+00:00

mssql_clustered=False on Index, UniqueConstraint,
PrimaryKeyConstraint now renders NONCLUSTERED.
The default of mssql_clustered is now None.

Co-Authored-By: mike bayer 
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

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

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

the new behavior of the autoincrement flag as per ref #3216

- reworked the way the "select_wraps_for" expression is

2016-02-21T01:22:38+00:00

handled within visit_select(); this attribute was added in the
1.0 series to accommodate the subquery wrapping behavior of
SQL Server and Oracle while also working with positional
column targeting and no longer relying upon "key fallback"
in order to target columns in such a statement.  The IBM DB2
third-party dialect also has this use case, but its implementation
is using regular expressions to rewrite the textual SELECT only
and does not make use of a "wrapped" select at this time.
The logic no longer attempts to reconcile proxy set collections as
this was not deterministic, and instead assumes that the select()
and the wrapper select() match their columns postionally,
at least for the column positions they have in common,
so it is now very simple and safe.  fixes #3657.
- as a side effect of #3657 it was also revealed that the
strategy of calling upon a ResultProxy._getter was not
correctly calling into NoSuchColumnError when an expected
column was not present, and instead returned None up to
loading.instances() to produce NoneType failures; added
a raiseerr argument to _getter() which is called when we
aren't expecting None, fixes #3658.

- add missing backend directives for SQL server

2016-02-08T19:20:12+00:00

- there was a DATEPART test after all, fix format

2016-01-14T22:50:03+00:00

- changelog for pr bitbucket:70, fixes #3624

2016-01-12T14:53:09+00:00

- A descriptive ValueError is now raised in the event that SQL server

2015-11-30T17:19:26+00:00

returns an invalid date or time format from a DATE or TIME
column, rather than failing with a NoneType error.  Pull request
courtesy Ed Avis.
pullreq github:206

- extend pullreq github:213 to also include DATETIMEOFFSET and TIME,

2015-11-14T17:38:45+00:00

which also accept zero precision
- extend test case here to include a backend-agnostic suite
- changelog for MSSQL date fix