summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/dialects
Commit message (Collapse)AuthorAgeFilesLines
* - Fixed bug where index reflection would mis-interpret indkey valuesMike Bayer2013-10-271-1/+4
| | | | | | | | | | when using the pypostgresql adapter, which returns these values as lists vs. psycopg2's return type of string. [ticket:2855] Conflicts: doc/build/changelog/changelog_09.rst lib/sqlalchemy/__init__.py
* - Fixed bug where Oracle table reflection using synonyms would failMike Bayer2013-10-251-5/+7
| | | | | if the synonym and the table were in different remote schemas. Patch to fix courtesy Kyle Derr. [ticket:2853]
* - attempt to clarify what mutable extension does for HSTORE, [ticket:2803]Mike Bayer2013-10-181-2/+9
|
* - Removed a 128-character truncation from the reflection of theMike Bayer2013-10-181-2/+1
| | | | | | 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-0/+56
| | | | | | | | | | | | | | | | | 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-2/+3
| | | | | | 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/+4
| | | | | 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-123-11/+11
| | | | | | | | | | | 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-2/+2
| | | | - use match with a .* preceding instead of search
* Merge pull request #26 from hackop/ticket_2819mike bayer2013-09-291-1/+1
| | | | re.match to re.search
* move FAQ to the docs, [ticket:2133]Mike Bayer2013-08-212-0/+4
| | | | | Conflicts: doc/build/index.rst
* Updates to MySQL reserved words for versions 5.5, 5.6, courtesyMike Bayer2013-07-311-0/+10
| | | | | | | | Hanno Schlichting. Also in 0.8.3, 0.7.11. [ticket:2791] Conflicts: doc/build/changelog/changelog_09.rst
* doc fixMike Bayer2013-07-121-1/+1
|
* The newly added SQLite DATETIME arguments storage_format andMike Bayer2013-07-121-0/+6
| | | | | | | 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]
* Added :class:`.BIGINT` to the list of type names that can beMike Bayer2013-07-021-2/+4
| | | | | reflected by the SQLite dialect; courtesy Russell Stuart. [ticket:2764]
* Added new flag ``retaining=False`` to the kinterbasdb and fdb dialects.Mike Bayer2013-06-303-45/+80
| | | | | | | 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]
* The behavior of :func:`.extract` has been simplified on theMike Bayer2013-06-281-22/+0
| | | | | | | | | | | | 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
* Type lookup when reflecting the Firebird types LONG andMike Bayer2013-06-281-7/+6
| | | | | | | | | | | INT64 has been fixed so that LONG is treated as INTEGER, INT64 treated as BIGINT, unless the type has a "precision" in which case it's treated as NUMERIC. Patch courtesy Russell Stuart. [ticket:2757] Conflicts: doc/build/changelog/changelog_09.rst
* Fixed bug in HSTORE type where keys/values that containedMike Bayer2013-06-281-3/+3
| | | | | | | | | | | 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
* - rework of correlation, continuing on #2668, #2746Mike Bayer2013-06-261-6/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | - add support for correlations to propagate all the way in; because correlations require context now, need to make sure a select enclosure of any level takes effect any number of levels deep. - fix what we said correlate_except() was supposed to do when we first released #2668 - "the FROM clause is left intact if the correlated SELECT is not used in the context of an enclosing SELECT..." - it was not considering the "existing_froms" collection at all, and prohibited additional FROMs from being placed in an any() or has(). - add test for multilevel any() - lots of docs, including glossary entries as we really need to define "WHERE clause", "columns clause" etc. so that we can explain correlation better - based on the insight that a SELECT can correlate anything that ultimately came from an enclosing SELECT that links to this one via WHERE/columns/HAVING/ORDER BY, have the compiler keep track of the FROM lists that correspond in this way, link it to the asfrom flag, so that we send to _get_display_froms() the exact list of candidate FROMs to correlate. no longer need any asfrom logic in the Select() itself - preserve 0.8.1's behavior for correlation when no correlate options are given, not to mention 0.7 and prior's behavior of not propagating implicit correlation more than one level.. this is to reduce surprises/hard-to-debug situations when a user isn't trying to correlate anything. Conflicts: doc/build/changelog/changelog_08.rst doc/build/changelog/changelog_09.rst lib/sqlalchemy/sql/compiler.py
* need the defaultdict import hereMike Bayer2013-06-261-0/+1
|
* Merge pull request #13 from malor/fix_indexes_reflectionmike bayer2013-06-261-14/+18
| | | | Fix indexes reflection in PostgreSQL
* 2.5ismMike Bayer2013-06-231-7/+7
|
* versionaddsMike Bayer2013-06-221-6/+33
|
* - 0.8 changelogMike Bayer2013-06-221-11/+11
| | | | - some whitespace
* Merge pull request #5 from cjw296/pg-rangesmike bayer2013-06-224-2/+246
| | | | Support for Postgres range types.
* fix up the isolation level docs which were a messMike Bayer2013-06-172-25/+58
|
* - changelogMike Bayer2013-06-152-3/+8
| | | | | | | - docs Conflicts: doc/build/changelog/changelog_09.rst
* Merge pull request #7 from malor/psycopg2_execution_optionsmike bayer2013-06-151-0/+1
| | | | Add AUTOCOMMIT isolation level support for psycopg2
* Merge pull request #3 from bslatkin/mastermike bayer2013-06-081-7/+16
| | | | Makes gaerdbms for App Engine use local MySQL server when running in dev_appserver2
* - changelog for [ticket:2704]Mike Bayer2013-06-081-9/+13
| | | | | | | - use an isinstance() check, concerned a TypeError might be indiscriminate Conflicts: doc/build/changelog/changelog_09.rst
* Fix using of 'mysql_length' for composite indexesRoman Podolyaka2013-06-081-7/+25
| | | | | | | | | | | | | | | | | 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/+16
| | | | | | | | | | | 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/+2
| | | | | | | | | | | :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
* add the py2k symbol from the 0.9 branch to support the hstore changeMike Bayer2013-05-291-0/+1
|
* - repair for py3kMike Bayer2013-05-291-1/+6
| | | | - fix test
* Unicode support for psycopg2 native hstore implementationDmitry Mugtasimov2013-05-291-1/+2
|
* hstores are text, and in py3k they seem to be implcitly unicode. soMike Bayer2013-05-291-10/+26
| | | | | add unicode encoding for py2k for the non-native hstore, pullreq for native psycopg2 support coming....
* 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]
* Updated mysqlconnector dialect to check for disconnect basedMike Bayer2013-04-291-1/+2
| | | | | on the apparent string message sent in the exception; tested against mysqlconnector 1.0.9.
* - fix long-outdated documentation for sql_mode/ansiquotes,Mike Bayer2013-04-291-26/+15
| | | | closes [ticket:1552]
* oracle doesn't have TRUE/FALSE, put 1/0 here, see how that goesMike Bayer2013-04-261-0/+6
|
* need to test for (list, tuple) here and not hasattr("__iter__")Mike Bayer2013-04-261-1/+4
| | | | since Py3K strings have __iter__
* - only search in the exception before the first newline, to avoidMike Bayer2013-04-231-2/+3
| | | | false positives for SQL statements containing certain text
* Opened up the checking for "disconnect" with psycopg2/libpqMike Bayer2013-04-221-18/+21
| | | | | | | | to check for all the various "disconnect" messages within the full exception hierarchy. Specifically the "closed the connection unexpectedly" message has now been seen in at least three different exception types. [ticket:2712]
* tweak this some more to handle the array being empty againMike Bayer2013-04-221-5/+3
|
* - change to [ticket:2681], pre-coerce the array to listMike Bayer2013-04-221-16/+6
| | | | unconditonally instead so that it works in all cases.
* The operators for the Postgresql ARRAY type supportsMike Bayer2013-04-221-1/+13
| | | | | | | | | | 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]
* - changelogMike Bayer2013-04-211-1/+1
| | | | - just do a fetchone() here, no need for len() etc.
* merge cymysql branchMike Bayer2013-04-212-1/+2
|\
View Lorry Controller Status