summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/dialects/mssql
Commit message (Collapse)AuthorAgeFilesLines
* - apply pep8 formatting to sqlalchemy/sql, sqlalchemy/util, sqlalchemy/dialects,Brian Jarrett2014-07-208-296/+354
| | | | sqlalchemy/orm, sqlalchemy/event, sqlalchemy/testing
* - Fixed a regression from 0.9.5 caused by :ticket:`3025` where theMike Bayer2014-07-141-0/+3
| | | | | | | 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"Mike Bayer2014-07-141-6/+12
| | | | | | | | | 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 implementationMike Bayer2014-07-141-1/+2
| | | | | | | | | 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
* - break up the <authors> copyright comment as part of a passMike Bayer2014-07-098-8/+16
| | | | to get all flake8 passing
* Merge pull request #98 from abbec/mssql2008-multivalues-insertmike bayer2014-07-061-0/+2
|\ | | | | Fixed support for multivalue inserts for MS SQL 2008
| * - Fixed support for multivalue inserts for MS SQL 2008 since it is actually ↵pr/98Albert Cervin2014-06-161-0/+2
| | | | | | | | supported.
* | - write some really complete docs on MSSQL autoincrement, fixes #3094Mike Bayer2014-06-241-10/+132
|/
* - more tests, including backend testsMike Bayer2014-05-161-17/+34
| | | | - implement for SQL server, use window functions when simple limit/offset not available
* Use _offset_clause and _limit_clause, which are always Visitable and usually ↵Dobes Vandermeer2014-04-251-3/+4
| | | | a BindParameter, instead of _offset and _limit in GenerativeSelect.
* - Revised the query used to determine the current default schema nameMike Bayer2014-04-171-14/+8
| | | | | | | to use the ``database_principal_id()`` function in conjunction with the ``sys.database_principals`` view so that we can determine the default schema independently of the type of login in progress (e.g., SQL Server, Windows, etc). fixes #3025
* take out the support paragraph and just put a basic introMike Bayer2014-03-091-9/+3
|
* dialects/mssql/pymssql.py: Remove second two paragraphs, as requested by ↵pr/75Marc Abramowitz2014-03-031-9/+0
| | | | @zzzeek.
* Update pymssql dialect description, remove "limitations" sectionMarc Abramowitz2014-02-271-9/+16
|
* Update URL for pymssqlMarc Abramowitz2014-02-271-1/+1
|
* - implement kwarg validation and type system for dialect-specificMike Bayer2014-01-181-7/+18
| | | | | arguments; [ticket:2866] - add dialect specific kwarg functionality to ForeignKeyConstraint, ForeignKey
* - changelog for pullreq:11Mike Bayer2014-01-181-1/+1
| | | | - be specific about version 0.9.2
* Bug Fix: Stop generating bad sql if an empty UniqueConstraint() is givendonkopotamus2014-01-171-0/+2
|
* Support mssql_clustered option on UniqueConstraint (plus docs and test)donkopotamus2014-01-171-4/+29
|
* Remove support for mssql_clustered on Tabledonkopotamus2014-01-171-15/+5
|
* Support mssql_clustered option in mssql dialect for both Table and ↵donkopotamus2014-01-141-8/+54
| | | | PrimaryKeyConstraint
* - happy new yearMike Bayer2014-01-058-8/+8
|
* - apply a similar fix for floats to mssql+pyodbc as we did to firebirdMike Bayer2013-12-281-3/+9
| | | | | - wrangle through osx+pyodbc+freetds to get at least test_suite to pass again with mssql+pyodbc. invovled adding some silly requirements
* Remove terminated connections from the pool.pr/51John Anderson2013-12-161-0/+1
| | | | | | In pymssql, if you terminate a long running query manually it will give you a connection reset by peer message, but this connection remains in the pool and will be re-used.
* Fix MSSQL dialects visit_drop_index to use the correct DDLdonkopotamus2013-12-051-5/+3
|
* - Fixed bug in default compiler plus those of postgresql, mysql, andMike Bayer2013-10-121-1/+1
| | | | | | | | mssql to ensure that any literal SQL expression values are rendered directly as literals, instead of as bound parameters, within a CREATE INDEX statement. [ticket:2742] - don't need expression_as_ddl(); literal_binds and include_table take care of this functionality.
* - A rework to the way that "quoted" identifiers are handled, in thatMike Bayer2013-08-271-2/+2
| | | | | | | | | | | | | | | | instead of relying upon various ``quote=True`` flags being passed around, these flags are converted into rich string objects with quoting information included at the point at which they are passed to common schema constructs like :class:`.Table`, :class:`.Column`, etc. This solves the issue of various methods that don't correctly honor the "quote" flag such as :meth:`.Engine.has_table` and related methods. The :class:`.quoted_name` object is a string subclass that can also be used explicitly if needed; the object will hold onto the quoting preferences passed and will also bypass the "name normalization" performed by dialects that standardize on uppercase symbols, such as Oracle, Firebird and DB2. The upshot is that the "uppercase" backends can now work with force-quoted names, such as lowercase-quoted names and new reserved words. [ticket:2812]
* - we dont actually need this unicode cast, on py3k + linux it seems theMike Bayer2013-07-092-8/+2
| | | | | has_table issues are OK. On OSX forget it. - still some issues with PY3k + pyodbc + decimal values it doesn't expect, not sure
* When querying the information schema on SQL Server 2000, removedMike Bayer2013-06-061-2/+15
| | | | | | | 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 reallyMike Bayer2013-06-031-0/+1
| | | | not happening too well (I need to stick with linux + freetds 0.91, I know)
* merge defaultMike Bayer2013-05-151-0/+6
|\
| * Regression from this ticket caused the unsupported keywordMike Bayer2013-05-151-0/+6
| | | | | | | | | | | | "true" to render, added logic to convert this to 1/0 for SQL server. [ticket:2682]
* | plugging awayMike Bayer2013-04-272-7/+6
| |
* | work through dialectsMike Bayer2013-04-272-5/+5
| |
* | - the raw 2to3 runMike Bayer2013-04-274-16/+16
|/ | | | - went through examples/ and cleaned out excess list() calls
* - this pymssql test needs to be against the pymssql dialectMike Bayer2013-04-181-0/+4
| | | | | | | | | | | | | - 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)Mike Bayer2013-03-291-0/+2
|\ | | | | | | Add disconnect check on timeouts
| * cleaned up errors, only check for connection timeout for nowJohn Anderson2013-03-181-3/+2
| |
| * Added disconnect checks for timeout, unable to read, and unable to writeJohn Anderson2013-03-181-0/+3
| |
* | dialects/mssql/pymssql.py: Modify module.Binary to work properly withMarc Abramowitz2013-03-181-1/+1
|/ | | | | | byte strings in Python 3 Fixes http://www.sqlalchemy.org/trac/ticket/2683
* - remove all compat items that are pre-2.5 (hooray)Mike Bayer2013-03-091-1/+1
| | | | | | - other cleanup - don't need compat.decimal, that approach never panned out. hopefully outside libs aren't pulling it in, they shouldn't be
* - replace mssql_ordering with generalized #695 solutionMike Bayer2013-01-201-10/+52
| | | | - documentation for mssql index options plus changelog and fixes
* Merged in dharland/sqlalchemy (pull request #35)Mike Bayer2013-01-201-0/+37
|\ | | | | | | Add extra mssql dialect options to Index
| * Add mssql_include option for mssql dialectDerek Harland2013-01-141-0/+10
| |
| * Add mssql_ordering option for mssql dialectDerek Harland2013-01-141-3/+10
| |
| * Add mssql_clustered option for mssql dialectDerek Harland2013-01-141-0/+20
| |
* | :class:`.Index` now supports arbitrary SQL expressions and/orMike Bayer2013-01-161-3/+2
|/ | | | | | | | functions, in addition to straight columns. Common modifiers include using ``somecolumn.desc()`` for a descending index and ``func.lower(somecolumn)`` for a case-insensitive index, depending on the capabilities of the target backend. [ticket:695]
* Added a py3K conditional around unnecessary .decode()Mike Bayer2013-01-121-0/+2
| | | | | call in mssql information schema, fixes reflection in Py3K. Also in 0.7.10. [ticket:2638]
* - changelog for pullreq 32Mike Bayer2013-01-121-124/+10
| | | | | | | | | | | - Fixed a regression whereby the "collation" parameter of the character types CHAR, NCHAR, etc. stopped working, as "collation" is now supported by the base string types. The TEXT, NCHAR, CHAR, VARCHAR types within the MSSQL dialect are now synonyms for the base types. - move out the type rendering tests into DB-agnostic tests and remove some of the old "create" statements. tests here are still very disorganized.
* Merged in dharland/sqlalchemy (pull request #32: Allow the MSSQL dialect to ↵Mike Bayer2013-01-121-12/+11
|\ | | | | | | support identity columns that are not part of the primary key)
View Lorry Controller Status