summaryrefslogtreecommitdiff
path: root/test/dialect
Commit message (Collapse)AuthorAgeFilesLines
* - Fixed bug where Oracle table reflection using synonyms would failMike Bayer2013-10-251-0/+29
| | | | | if the synonym and the table were in different remote schemas. Patch to fix courtesy Kyle Derr. [ticket:2853]
* - Removed a 128-character truncation from the reflection of theMike Bayer2013-10-181-0/+11
| | | | | | server default for a column; this code was original from PG system views which truncated the string for readability. [ticket:2844]
* - The change in :ticket:`2721`, which is that the ``deferrable`` keywordMike Bayer2013-10-181-3/+51
| | | | | | | | | | | | | | | | | of :class:`.ForeignKeyConstraint` is silently ignored on the MySQL backend, will be reverted as of 0.9; this keyword will now render again, raising errors on MySQL as it is not understood - the same behavior will also apply to the ``initially`` keyword. In 0.8, the keywords will remain ignored but a warning is emitted. Additionally, the ``match`` keyword now raises a :class:`.CompileError` on 0.9 and emits a warning on 0.8; this keyword is not only silently ignored by MySQL but also breaks the ON UPDATE/ON DELETE options. To use a :class:`.ForeignKeyConstraint` that does not render or renders differently on MySQL, use a custom compilation option. An example of this usage has been added to the documentation, see :ref:`mysql_foreign_keys`. [ticket:2721] [ticket:2839]
* MySQL-connector dialect now allows options in the create_engineMike Bayer2013-10-131-5/+54
| | | | | | query string to override those defaults set up in the connect, including "buffered" and "raise_on_warnings". [ticket:2515]
* Parenthesis will be applied to a compound SQL expression asMike Bayer2013-10-121-1/+12
| | | | | rendered in the column list of a CREATE INDEX statement. [ticket:2742]
* - Fixed bug in default compiler plus those of postgresql, mysql, andMike Bayer2013-10-124-0/+41
| | | | | | | | | | | 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. Conflicts: lib/sqlalchemy/sql/util.py
* - put exact version string in the testMike Bayer2013-09-291-3/+2
| | | | - use match with a .* preceding instead of search
* add test for upcoming pullreqMike Bayer2013-09-291-1/+6
|
* 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. [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/+7
| | | | | 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
|
* fix 2.5 syntaxesMike Bayer2013-06-293-4/+6
|
* 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] Conflicts: doc/build/changelog/changelog_09.rst
* refactor test suites for postgresql, mssql, mysql into packages.Mike Bayer2013-06-2821-7354/+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] Conflicts: doc/build/changelog/changelog_09.rst lib/sqlalchemy/dialects/postgresql/hstore.py
* Merge pull request #5 from cjw296/pg-rangesmike bayer2013-06-221-1/+329
| | | | Support for Postgres range types.
* Merge pull request #7 from malor/psycopg2_execution_optionsmike bayer2013-06-151-0/+10
| | | | Add AUTOCOMMIT isolation level support for psycopg2
* 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] Conflicts: doc/build/changelog/changelog_09.rst lib/sqlalchemy/dialects/mssql/information_schema.py
* 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] Conflicts: doc/build/changelog/changelog_09.rst
* - 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....
* Add missing import that caused test_notice_logging to fail if this suite was ↵Chris Withers2013-05-261-0/+1
| | | | run on its own.
* 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]
* 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
| |
* | 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.
* 0.8.1 bump + test, changelog for hstore fix [ticket:2680]Mike Bayer2013-03-181-0/+6
|
* Added support for Postgresql's traditional SUBSTRINGMike Bayer2013-03-091-0/+8
| | | | | | | function syntax, renders as "SUBSTRING(x FROM y FOR z)" when regular ``func.substring()`` is used. Also in 0.7.11. Courtesy Gunnlaugur Por Briem. [ticket:2676]
* - remove all compat items that are pre-2.5 (hooray)Mike Bayer2013-03-093-9/+6
| | | | | | - other cleanup - don't need compat.decimal, that approach never panned out. hopefully outside libs aren't pulling it in, they shouldn't be
* test for cymysqlHajime Nakagami2013-02-171-0/+1
|
* The :meth:`.ColumnOperators.in_` operator will now coerceMike Bayer2013-02-021-0/+4
| | | | | values of ``None`` to :func:`.null`. [ticket:2496]
* Add ANY/ALL construct support for PostgreSQL's ARRAY typeAudrius Kažukauskas2013-01-281-1/+49
|
* - replace mssql_ordering with generalized #695 solutionMike Bayer2013-01-201-1/+1
| | | | - documentation for mssql index options plus changelog and fixes
* Merged in dharland/sqlalchemy (pull request #35)Mike Bayer2013-01-201-0/+36
|\ | | | | | | Add extra mssql dialect options to Index
| * Add mssql_include option for mssql dialectDerek Harland2013-01-141-0/+18
| |
| * Add mssql_ordering option for mssql dialectDerek Harland2013-01-141-0/+9
| |
View Lorry Controller Status