summaryrefslogtreecommitdiff
path: root/test/dialect
Commit message (Collapse)AuthorAgeFilesLines
* 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
| |
| * Add mssql_clustered option for mssql dialectDerek Harland2013-01-141-0/+9
| |
* | - "postgres_where" has been removedMike Bayer2013-01-161-11/+0
|/
* 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.
* Merged in dharland/sqlalchemy (pull request #32: Allow the MSSQL dialect to ↵Mike Bayer2013-01-121-0/+24
|\ | | | | | | support identity columns that are not part of the primary key)
| * Add several MSSQL dialect tests for sequence declarationsDerek Harland2012-12-041-0/+24
| |
* | Fixed bug in :func:`.postgresql.array` construct whereby using itMike Bayer2013-01-021-0/+9
| | | | | | | | | | inside of an :func:`.expression.insert` construct would produce an error regarding a parameter issue in the ``self_group()`` method.
* | More adjustment to this SQLite related issue which was released inMike Bayer2012-12-141-2/+26
| | | | | | | | | | | | | | 0.7.9, to intercept legacy SQLite quoting characters when reflecting foreign keys. In addition to intercepting double quotes, other quoting characters such as brackets, backticks, and single quotes are now also intercepted. [ticket:2568]
* | add futureMike Bayer2012-12-111-0/+1
| |
* | Fixed table reflection for Oracle when accessing a synonym that refersMike Bayer2012-12-091-0/+39
| | | | | | | | | | | | | | | | | | | | to a DBLINK remote database; while the syntax has been present in the Oracle dialect for some time, up until now it has never been tested. The syntax has been tested against a sample database linking to itself, however there's still some uncertainty as to what should be used for the "owner" when querying the remote database for table information. Currently, the value of "username" from user_db_links is used to match the "owner". [ticket:2619]
* | - multivalued inserts, [ticket:2623]Mike Bayer2012-12-081-25/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - update "not supported" messages for empty inserts, mutlivalue inserts - rework the ValuesBase approach for multiple value sets so that stmt.parameters does store a list for multiple values; the _has_multiple_parameters flag now indicates which of the two modes the statement is within. it now raises exceptions if a subsequent call to values() attempts to call a ValuesBase with one mode in the style of the other mode; that is, you can't switch a single- or multi- valued ValuesBase to the other mode, and also if a multiple value is passed simultaneously with a kwargs set. Added tests for these error conditions - Calling values() multiple times in multivalue mode now extends the parameter list to include the new parameter sets. - add error/test if multiple *args were passed to ValuesBase.values() - rework the compiler approach for multivalue inserts, back to where _get_colparams() returns the same list of (column, value) as before, thereby maintaining the identical number of append() and other calls when multivalue is not enabled. In the case of multivalue, it makes a last-minute switch to return a list of lists instead of the single list. As it constructs the additional lists, the inline defaults and other calculated default parameters of the first parameter set are copied into the newly generated lists so that these features continue to function for a multivalue insert. Multivalue inserts now add no additional function calls to the compilation for regular insert constructs. - parameter lists for multivalue inserts now includes an integer index for all parameter sets. - add detailed documentation for ValuesBase.values(), including careful wording to describe the difference between multiple values and an executemany() call. - add a test for multivalue insert + returning - it works ! - remove the very old/never used "postgresql_returning"/"firebird_returning" flags.
* | The Oracle LONG type, while an unbounded text type, does not appearMike Bayer2012-12-061-0/+15
| | | | | | | | | | | | | | to use the cx_Oracle.LOB type when result rows are returned, so the dialect has been repaired to exclude LONG from having cx_Oracle.LOB filtering applied. Also in 0.7.10. [ticket:2620]
* | Repaired the usage of ``.prepare()`` in conjunction withMike Bayer2012-12-061-0/+70
|/ | | | | | | | | | | cx_Oracle so that a return value of ``False`` will result in no call to ``connection.commit()``, hence avoiding "no transaction" errors. Two-phase transactions have now been shown to work in a rudimental fashion with SQLAlchemy and cx_oracle, however are subject to caveats observed with the driver; check the documentation for details. Also in 0.7.10. [ticket:2611]
* HSTORE.comparator_factory should subclass Concatenable.ComparatorAudrius Kažukauskas2012-11-211-2/+4
|
* Add special containment operation methods for PG array typeAudrius Kažukauskas2012-11-201-12/+69
|
* another hide from 2to3 testMike Bayer2012-11-181-1/+2
|
* Fixed a gotcha where inadvertently calling list() on aMike Bayer2012-11-181-1/+2
| | | | | | :class:`.ColumnElement` would go into an endless loop, if :meth:`.ColumnOperators.__getitem__` were implemented. A new NotImplementedError is emitted via ``__iter__()``.
* - hstore documentation, migrationMike Bayer2012-11-171-3/+37
| | | | - don't need a custom exception here, just use ValueError
* - hstore adjustmentsMike Bayer2012-11-171-0/+128
|
* Add PostgreSQL HStore type supportAudrius Kažukauskas2012-11-131-1/+191
|
* Fixed bug in type_coerce() whereby typing informationMike Bayer2012-11-121-1/+10
| | | | | | | | could be lost if the statement were used as a subquery inside of another statement, as well as other similar situations. Among other things, would cause typing information to be lost when the Oracle/mssql dialects would apply limit/offset wrappings. [ticket:2603]
* - move out maxdbMike Bayer2012-10-181-239/+0
| | | | | | - begin consolidating docs for dialects to be more self contained - add a separate section for "external" dialects - not sure how we're going to go with this yet.
* - [feature] Added "collation" parameter to allMike Bayer2012-10-101-1/+5
| | | | | | | | | | | String types. When present, renders as COLLATE <collation>. This to support the COLLATE keyword now supported by several databases including MySQL, SQLite, and Postgresql. [ticket:2276] - [change] The Text() type renders the length given to it, if a length was specified.
* - [feature] Added TIME type to mysql dialect,Mike Bayer2012-10-101-317/+222
| | | | | | | | | | | | accepts "fst" argument which is the new "fractional seconds" specifier for recent MySQL versions. The datatype will interpret a microseconds portion received from the driver, however note that at this time most/all MySQL DBAPIs do not support returning this value. [ticket:2534] - attempted to modernize the types tests in test_mysql a little, though has a long way to go
* - [feature] the MS Access dialect has beenMike Bayer2012-09-301-31/+0
| | | | | | | | | | moved to its own project on Bitbucket, taking advantage of the new SQLAlchemy dialect compliance suite. The dialect is still in very rough shape and probably not ready for general use yet, however it does have *extremely* rudimental functionality now.
* - [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]
View Lorry Controller Status