summaryrefslogtreecommitdiff
path: root/test/dialect/test_mssql.py
Commit message (Collapse)AuthorAgeFilesLines
* refactor test suites for postgresql, mssql, mysql into packages.Mike Bayer2013-06-281-2143/+0
|
* When querying the information schema on SQL Server 2000, removedMike Bayer2013-06-061-2/+24
| | | | | | | 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]
* mssql test fixesMike Bayer2013-05-261-6/+6
|
* merge defaultMike Bayer2013-05-151-0/+11
|\
| * Regression from this ticket caused the unsupported keywordMike Bayer2013-05-151-0/+11
| | | | | | | | | | | | "true" to render, added logic to convert this to 1/0 for SQL server. [ticket:2682]
* | - the raw 2to3 runMike Bayer2013-04-271-15/+15
|/ | | | - went through examples/ and cleaned out excess list() calls
* - this pymssql test needs to be against the pymssql dialectMike Bayer2013-04-181-1/+1
| | | | | | | | | | | | | - 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]
* - test all pymssql messages hereMike Bayer2013-03-291-7/+23
| | | | - changelog
* Merged in sontek/sqlalchemy/add_better_disconnect_checks (pull request #47)Mike Bayer2013-03-291-0/+6
|\ | | | | | | Add disconnect check on timeouts
| * cleaned up errors, only check for connection timeout for nowJohn Anderson2013-03-181-2/+2
| |
| * Added disconnect checks for timeout, unable to read, and unable to writeJohn Anderson2013-03-181-0/+6
| |
* | Make MonkeyPatchedBinaryTest not fail on Python 2.5 (which doesn't haveMarc Abramowitz2013-03-201-1/+2
| | | | | | | | the `b` notation for byte string literals)
* | Make MonkeyPatchedBinaryTest only run when using mssql. Prevents failedMarc Abramowitz2013-03-181-0/+2
| | | | | | | | tests when using a different dialect.
* | Add a test for http://www.sqlalchemy.org/trac/ticket/2683Marc Abramowitz2013-03-181-0/+13
|/ | | | This test currently passes in Python 2 but fails in Python 3.
* - remove all compat items that are pre-2.5 (hooray)Mike Bayer2013-03-091-3/+2
| | | | | | - other cleanup - don't need compat.decimal, that approach never panned out. hopefully outside libs aren't pulling it in, they shouldn't be
* The :meth:`.ColumnOperators.in_` operator will now coerceMike Bayer2013-02-021-0/+4
| | | | | values of ``None`` to :func:`.null`. [ticket:2496]
* - replace mssql_ordering with generalized #695 solutionMike Bayer2013-01-201-1/+1
| | | | - documentation for mssql index options plus changelog and fixes
* Add mssql_include option for mssql dialectDerek Harland2013-01-141-0/+18
|
* Add mssql_ordering option for mssql dialectDerek Harland2013-01-141-0/+9
|
* Add mssql_clustered option for mssql dialectDerek Harland2013-01-141-0/+9
|
* Added a py3K conditional around unnecessary .decode()Mike Bayer2013-01-121-0/+7
| | | | | call in mssql information schema, fixes reflection in Py3K. Also in 0.7.10. [ticket:2638]
* - changelog for pullreq 32Mike Bayer2013-01-121-203/+241
| | | | | | | | | | | - 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.
* Add several MSSQL dialect tests for sequence declarationsDerek Harland2012-12-041-0/+24
|
* - [bug] Fixed compiler bug whereby using a correlatedMike Bayer2012-09-301-0/+21
| | | | | | | subquery within an ORDER BY would fail to render correctly if the stament also used LIMIT/OFFSET, due to mis-rendering within the ROW_NUMBER() OVER clause. Fix courtesy sayap [ticket:2538]
* getting everything to pass againMike Bayer2012-09-271-1/+3
|
* trying different approaches to test layout. in this one, the testing modulesMike Bayer2012-09-271-4/+4
| | | | | | | become an externally usable package but still remains within the main sqlalchemy parent package. in this system, we use kind of an ugly hack to get the noseplugin imported outside of the "sqlalchemy" package, while still making it available within sqlalchemy for usage by third party libraries.
* test fixesMike Bayer2012-09-221-4/+5
|
* - further mxodbc tweaks affecting other test suitesMike Bayer2012-09-021-9/+0
|
* - [bug] Fixed compiler bug whereby a givenMike Bayer2012-08-121-8/+11
| | | | | | select() would be modified if it had an "offset" attribute, causing the construct to not compile correctly a second time. [ticket:2545]
* - adjustments for py3.3 unit tests, [ticket:2542]Mike Bayer2012-08-111-2/+3
|
* - [feature] SQL Server dialect can be givenMike Bayer2012-08-071-0/+35
| | | | | | | | | | | database-qualified schema names, i.e. "schema='mydatabase.dbo'"; reflection operations will detect this, split the schema among the "." to get the owner separately, and emit a "USE mydatabase" statement before reflecting targets within the "dbo" owner; the existing database returned from DB_NAME() is then restored.
* - more import cleanup for MSSQLMike Bayer2012-08-071-1/+2
|
* trailing whitespace bonanzaMike Bayer2012-07-281-25/+25
|
* - [bug] removed legacy behavior wherebyMike Bayer2012-04-241-6/+5
| | | | | | | | | | a column comparison to a scalar SELECT via == would coerce to an IN with the SQL server dialect. This is implicit behavior which fails in other scenarios so is removed. Code which relies on this needs to be modified to use column.in_(select) explicitly. [ticket:2277]
* - [bug] UPDATE..FROM syntax with SQL ServerMike Bayer2012-04-181-1/+1
| | | | | | | | | | requires that the updated table be present in the FROM clause when an alias of that table is also present in the FROM clause. The updated table is now always present in the FROM, when FROM is present in the first place. Courtesy sayap. [ticket:2468]
* - [bug] Repaired the use_scope_identityMike Bayer2012-04-051-1/+23
| | | | | | | | | | create_engine() flag when using the pyodbc dialect. Previously this flag would be ignored if set to False. When set to False, you'll get "SELECT @@identity" after each INSERT to get at the last inserted ID, for those tables which have "implicit_returning" set to False.
* - [feature] Added support for MSSQL INSERT,Mike Bayer2012-03-131-0/+90
| | | | | | UPDATE, and DELETE table hints, using new with_hint() method on UpdateBase. [ticket:2430]
* - [bug] Adjusted the regexp used in theMike Bayer2012-01-221-0/+17
| | | | | | | | | | mssql.TIME type to ensure only six digits are received for the "microseconds" portion of the value, which is expected by Python's datetime.time(). Note that support for sending microseconds doesn't seem to be possible yet with pyodbc at least. [ticket:2340]
* - [bug] repaired the with_hint() feature whichMike Bayer2011-12-031-0/+29
| | | | | | | | wasn't implemented correctly on MSSQL - usually used for the "WITH (NOLOCK)" hint (which you shouldn't be using anyway ! use snapshot isolation instead :) ) [ticket:2336]
* - The behavior of =/!= when comparing a scalar selectMike Bayer2011-09-231-4/+5
| | | | | | | | | | | to a value will no longer produce IN/NOT IN as of 0.8; this behavior is a little too heavy handed (use in_() if you want to emit IN) and now emits a deprecation warning. To get the 0.8 behavior immediately and remove the warning, a compiler recipe is given at http://www.sqlalchemy.org/docs/07/dialects/mssql.html#scalar-select-comparisons to override the behavior of visit_binary(). [ticket:2277]
* - Query will convert an OFFSET of zero whenMike Bayer2011-08-061-3/+28
| | | | | | | | slicing into None, so that needless OFFSET clauses are not invoked. - mssql: "0" is accepted as an argument for limit() which will produce "TOP 0". [ticket:2222] - add tests to default compiler test for LIMIT/OFFSET generation
* add test for [ticket:2159]rel_0_7_1Mike Bayer2011-06-051-2/+4
|
* - Fixed bug in MSSQL dialect whereby the aliasingMike Bayer2011-05-191-57/+74
| | | | | | applied to a schema-qualified table would leak into enclosing select statements [ticket:2169]. Also in 0.6.8.
* - remove test.sql._base, test.engine._base, test.orm._base, move those ↵Mike Bayer2011-03-271-12/+12
| | | | | | | classes to a new test.lib.fixtures module - move testing.TestBase to test.lib.fixtures - massive search and replace
* - convert @provide_metadata to use self accessMike Bayer2011-03-261-0/+5
| | | | | - having occasional issues with BasicEntity grabbing, if it persists may have to pass an explicit base class into setup_classes()/setup_mappers()
* whoops, only on SQL serverMike Bayer2011-03-181-0/+2
|
* - Rewrote the query used to get the definition of a view,Mike Bayer2011-03-161-1/+35
| | | | | | | typically when using the Inspector interface, to use sys.sql_modules instead of the information schema, thereby allowing views definitions longer than 4000 characters to be fully returned. [ticket:2071]
* - mssql VARBINARY emits 'max' for length when no length specified, as isMike Bayer2011-02-101-3/+3
| | | | the case already for VARCHAR, NVARCHAR [ticket:1833]
* - A TypeDecorator of Integer can be used with a primary keyMike Bayer2011-01-111-1/+1
| | | | | | | | | | | | | | | | | | | column, and the "autoincrement" feature of various dialects as well as the "sqlite_autoincrement" flag will honor the underlying database type as being Integer-based. [ticket:2005] - Result-row processors are applied to pre-executed SQL defaults, as well as cursor.lastrowid, when determining the contents of result.inserted_primary_key. [ticket:2006] - Bind parameters present in the "columns clause" of a select are now auto-labeled like other "anonymous" clauses, which among other things allows their "type" to be meaningful when the row is fetched, as in result row processors. - TypeDecorator is present in the "sqlalchemy" import space.
* - whitespace removal bonanzaMike Bayer2011-01-021-43/+43
|
View Lorry Controller Status