summaryrefslogtreecommitdiff
path: root/test/dialect
Commit message (Collapse)AuthorAgeFilesLines
* - Removed some now unneeded version checks [ticket:2829] courtesy alex gaynorMike Bayer2013-09-221-2/+0
|
* The newly added SQLite DATETIME arguments storage_format andMike Bayer2013-07-121-1/+46
| | | | | | | regexp apparently were not fully implemented correctly; while the arguments were accepted, in practice they would have no effect; this has been fixed. Also in 0.8.3. [ticket:2781]
* for this test, apparently we don't handle sets as unordered since neither doesMike Bayer2013-07-021-3/+9
| | | | | MySQL. for some reason set ordering was constant when testing mysqldb, but not so with oursql.
* Added :class:`.BIGINT` to the list of type names that can beMike Bayer2013-07-021-1/+3
| | | | | reflected by the SQLite dialect; courtesy Russell Stuart. [ticket:2764]
* Added new flag ``retaining=False`` to the kinterbasdb and fdb dialects.Mike Bayer2013-06-301-0/+73
| | | | | | | This controls the value of the ``retaining`` flag sent to the ``commit()`` and ``rollback()`` methods of the DBAPI connection. Defaults to False. Also in 0.8.2, where it defaults to True. [ticket:2763]
* - replace most explicitly-named test objects called "Mock..." withMike Bayer2013-06-302-65/+33
| | | | | | | | | | | | actual mock objects from the mock library. I'd like to use mock for new tests so we might as well use it in obvious places. - use unittest.mock in py3.3 - changelog - add a note to README.unittests - add tests_require in setup.py - have tests import from sqlalchemy.testing.mock - apply usage of mock to one of the event tests. we can be using this approach all over the place.
* set UTC timezone on the connection here so we can get consistent resultsMike Bayer2013-06-291-6/+9
|
* The behavior of :func:`.extract` has been simplified on theMike Bayer2013-06-282-56/+161
| | | | | | | | | Postgresql dialect to no longer inject a hardcoded ``::timestamp`` or similar cast into the given expression, as this interfered with types such as timezone-aware datetimes, but also does not appear to be at all necessary with modern versions of psycopg2. Also in 0.8.2. [ticket:2740]
* refactor test suites for postgresql, mssql, mysql into packages.Mike Bayer2013-06-2821-7350/+7449
|
* Fixed bug in HSTORE type where keys/values that containedMike Bayer2013-06-281-0/+37
| | | | | | | backslashed quotes would not be escaped correctly when using the "non native" (i.e. non-psycopg2) means of translating HSTORE data. Patch courtesy Ryan Kelly. [ticket:2766]
* YEAR(2) emits a warning and oursql / mysqlconnector throw an exceptionMike Bayer2013-06-231-4/+2
| | | | on the warning so just dump it
* Fix unicode literals on Python 3.1 and 3.2pr/10Roman Podolyaka2013-06-231-8/+8
| | | | | A few tests use u'' unicode literals which are not supported in Python versions 3.1 and 3.2.
* this locale is not needed. maybe it is somewhere but the locale I have ↵Mike Bayer2013-06-221-13/+9
| | | | | | ("C", whatever that means, cannot find meaning of this anywhere in Postgresql documentation) seems to work
* Merge pull request #5 from cjw296/pg-rangesmike bayer2013-06-221-1/+329
|\ | | | | Support for Postgres range types.
| * Implement EXCLUDE constraints for postgres.Chris Withers2013-06-101-1/+49
| |
| * add support for range operators listed in ↵Chris Withers2013-06-101-1/+159
| | | | | | | | http://www.postgresql.org/docs/9.2/interactive/functions-range.html
| * Basic type support for the new range types in postgres 9.2Chris Withers2013-06-101-1/+123
| |
* | can remove this, issue is fixedMike Bayer2013-06-171-10/+1
| |
* | - clean up this test (really we don't even need this, it's not testing much)Mike Bayer2013-06-161-13/+20
| | | | | | | | | | - for the moment, put a catch in it to see if we can trap that issue on jenkins
* | Add AUTOCOMMIT isolation level support for psycopg2pr/7Roman Podolyaka2013-06-151-0/+10
|/ | | | | | | | | | | | | | One can use this to emit statements, which can not be executed within a transaction (e. g. CREATE DATABASE): from sqlalchemy import create_engine eng = create_engine('postgresql://test:test@localhost/test') conn = eng.connect().execution_options(isolation_level='AUTOCOMMIT') conn.execute('CREATE DATABASE test2;') Fixes issue #2072.
* get nested joins to render on oracle 8Mike Bayer2013-06-081-0/+33
|
* most of these dialect=mysql.dialect() calls are redundantMike Bayer2013-06-081-23/+13
|
* Fix using of 'mysql_length' for composite indexesRoman Podolyaka2013-06-081-0/+29
| | | | | | | | | | | | | | | | | Currently, one can specify the prefix length for an index column using 'mysql_length' keyword argument when creating an Index instance. But in case of composite indexes the prefix length value is applied only to the last column. Extend the existing API in way so that 'mysql_length' argument value can be either: - an integer specifying the same prefix length value for each column of an index - a (column_name --> integer value) mapping specifying the prefix length value for each column of an index separately Fixes issue #2704.
* 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]
* The ``deferrable`` keyword argument on :class:`.ForeignKey` andMike Bayer2013-06-031-0/+13
| | | | | | | | :class:`.ForeignKeyConstraint` will not render the ``DEFERRABLE`` keyword on the MySQL dialect. For a long time we left this in place because a non-deferrable foreign key would act very differently than a deferrable one, but some environments just disable FKs on MySQL, so we'll be less opinionated here. [ticket:2721]
* - repair for py3kMike Bayer2013-05-291-2/+2
| | | | - fix test
* hstores are text, and in py3k they seem to be implcitly unicode. soMike Bayer2013-05-291-0/+25
| | | | | add unicode encoding for py2k for the non-native hstore, pullreq for native psycopg2 support coming....
* mssql test fixesMike Bayer2013-05-261-6/+6
|
* - oracle tests passing in py3k!!Mike Bayer2013-05-261-6/+7
|
* a few more oracle fixesMike Bayer2013-05-261-1/+2
|
* cleanup for oracleMike Bayer2013-05-261-10/+11
|
* - add a test specific to sqlite testing cursor.description encoding (shouldMike Bayer2013-05-261-1/+22
| | | | | probably be one in test_query or test_unicode...) - fix up test_unitofwork
* postgresql testsMike Bayer2013-05-261-6/+6
|
* mysql testsMike Bayer2013-05-261-13/+14
|
* Merge branch 'master' into rel_0_9Mike Bayer2013-05-261-0/+1
|\
| * Add missing import that caused test_notice_logging to fail if this suite was ↵Chris Withers2013-05-261-0/+1
| | | | | | | | run on its own.
* | sqlite testsMike Bayer2013-05-261-5/+5
| |
* | merge defaultMike Bayer2013-05-152-0/+21
|\ \ | |/
| * Regression from this ticket caused the unsupported keywordMike Bayer2013-05-152-0/+21
| | | | | | | | | | | | "true" to render, added logic to convert this to 1/0 for SQL server. [ticket:2682]
* | postgresql dialect testsMike Bayer2013-04-281-29/+30
| |
* | - the raw 2to3 runMike Bayer2013-04-277-77/+77
|/ | | | - went through examples/ and cleaned out excess list() calls
* tweak this some more to handle the array being empty againMike Bayer2013-04-221-0/+11
|
* - change to [ticket:2681], pre-coerce the array to listMike Bayer2013-04-221-10/+3
| | | | unconditonally instead so that it works in all cases.
* The operators for the Postgresql ARRAY type supportsMike Bayer2013-04-221-60/+106
| | | | | | | | | | input types of sets, generators, etc. but only when a dimension is specified for the ARRAY; otherwise, the dialect needs to peek inside of "arr[0]" to guess how many dimensions are in use. If this occurs with a non list/tuple type, the error message is now informative and directs to specify a dimension for the ARRAY. [ticket:2681]
* - establish ordering here for the hstore repr testMike Bayer2013-04-201-4/+5
|
* - 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
| |
View Lorry Controller Status