summaryrefslogtreecommitdiff
path: root/lib
Commit message (Collapse)AuthorAgeFilesLines
* - work from an "explicit is better than implicit" perspectiveMike Bayer2015-11-253-65/+74
| | | | | here and require a flag on update() to use parameter ordering rather than table ordering. more docs/changelog notes are needed
* Merge remote-tracking branch 'origin/pr/200' into pr200Mike Bayer2015-11-254-34/+68
|\
| * Reduce the numbers of calls to isinstancepr/200Gorka Eguileor2015-10-081-34/+32
| | | | | | | | | | Change _process_colparams method to remove duplicate isinstance calls and try to speed up processing of the parameters.
| * Remove dict comprehension for py26 compatibilityGorka Eguileor2015-10-052-5/+5
| | | | | | | | | | Remove added dict comprehensions that make this patch set non python 2.6 compatible.
| * Only check once if parameters are orderedGorka Eguileor2015-10-023-35/+35
| | | | | | | | | | | | Instead of checking multiple times if parameters are a dictionary in the form of a tuple or list of value pairs, we check it only once and then store it in the statement so it can be used on compilation time.
| * Postpone parameters change in ordered updatesGorka Eguileor2015-09-304-18/+15
| | | | | | | | | | | | | | Postpone as much as possible the change of update parameters to OrderedDict from list or tuple of pairs. This way we won't have problems with query's update method.
| * Only preserve order in updates if tuple/dictGorka Eguileor2015-09-295-24/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To avoid penalties for updates that do not require ordering, we will only use OrderedDict for updates that receive a tuple or list of pairs, and all kinds of dictionaries (dict, sqlalchemy's OrderedDict, or collections.OrderedDict) will be treateated as unordered updates, just like we were doing before. This way this new feature will not change how updates behave for any existing code and will only affect those that use the new ordered feature. This patch reverts update tests to how they were before as well as adds a couple of tests to confirm that OrderedDicts are really treated like normal dicts.
| * Preserve order in update methodGorka Eguileor2015-09-244-12/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In some DBs the UPDATE operation is order dependent, so the operation behaves differently depending on the order of the values. As an example, imagine a volumes table with columns 'status' and 'previous_status' and we want to update a volume that has 'available' in the status column. If the SQL query is performed as: UPDATE volumes SET previous_status=status, status='new' WHERE id=1; This will result in a volume with 'new' status and 'available' previous_status both on SQLite and MariaDB, but if we reverse the columns: UPDATE volumes SET status='new', previous_status=status WHERE id=1; We will get the same result in SQLite but will result in a volume with status and previous_status set to 'new' in MariaDB, which is not what we want. So order must be taken into consideration in some cases and it should be allowed to ve specified via the Query update method or the values method of an update. This patch fixes this issue by preserving the order of parameters in updates and allowing to receive not only dictionaries in update and values but also ordered dictionaries and list/tuples of value pairs (like dict and OrderedDict do). fixes #3541
* | - Fixed bug which is actually a regression that occurred betweenMike Bayer2015-11-252-2/+15
| | | | | | | | | | | | | | | | versions 0.8.0 and 0.8.1, due :ticket:`2714`. The case where joined eager loading needs to join out over a subclass-bound relationship when "with_polymorphic" were also used would fail to join from the correct entity. fixes #3593
* | - support declarativemappedtest with per-test setupMike Bayer2015-11-251-0/+10
| |
* | - Change "expr" to "entity" for example illustrating an eventBas van den Heuvel2015-11-241-1/+1
| | | | | | | | that intercepts a query and adds entity-oriented criteria
* | - Fixed joinedload bug which would occur when a. the query includesMike Bayer2015-11-211-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | limit/offset criteria that forces a subquery b. the relationship uses "secondary" c. the primaryjoin of the relationship refers to a column that is either not part of the primary key, or is a PK col in a joined-inheritance subclass table that is under a different attribute name than the parent table's primary key column d. the query defers the columns that are present in the primaryjoin, typically via not being included in load_only(); the necessary column(s) would not be present in the subquery and produce invalid SQL. fixes #3592
* | - A rare case which occurs when a :meth:`.Session.rollback` fails in theMike Bayer2015-11-192-3/+15
| | | | | | | | | | | | | | | | | | | | | | | | scope of a :meth:`.Session.flush` operation that's raising an exception, as has been observed in some MySQL SAVEPOINT cases, prevents the original database exception from being observed when it was emitted during flush, but only on Py2K because Py2K does not support exception chaining; on Py3K the originating exception is chained. As a workaround, a warning is emitted in this specific case showing at least the string message of the original database error before we proceed to raise the rollback-originating exception. fixes #2696
* | - Fixed the ``.python_type`` attribute of :class:`.postgresql.INTERVAL`Mike Bayer2015-11-191-0/+6
| | | | | | | | | | | | | | | | | | to return ``datetime.timedelta`` in the same way as that of :obj:`.types.Interval.python_type`, rather than raising ``NotImplementedError``. fixes #3571 (cherry picked from commit 29d6f6e19b014bb5ce79032bd8803e32b4da0e5e)
* | - rewrite the docs and add a test for the bake_queries=TrueMike Bayer2015-11-191-5/+21
| | | | | | | | | | | | | | relationship flag; this flag *does* have an effect when the baked lazy loader plugin has been invoked. clarify the intent of this flag as an "opt out" but only has an effect when the baked system is loaded anyway. fixes #3572
* | - Added support for reflecting the source of materialized viewsMike Bayer2015-11-181-5/+21
| | | | | | | | | | | | to the Postgresql version of the :meth:`.Inspector.get_view_definition` method. fixes #3587
* | - extend pullreq github:213 to also include DATETIMEOFFSET and TIME,Mike Bayer2015-11-141-2/+2
| | | | | | | | | | | | which also accept zero precision - extend test case here to include a backend-agnostic suite - changelog for MSSQL date fix
* | Merge remote-tracking branch 'origin/pr/213' into pr213Mike Bayer2015-11-141-1/+1
|\ \
| * | Pass precision value to mssql.DATETIME2 when it is 0pr/213Jacobo de Vera2015-11-131-1/+1
| | | | | | | | | | | | | | | The simple check on the precision results in DATETIME2(0) generating a DATETIME2 column, with default precision, which is 7.
* | | - fix missing argument in TypeDecorator.copy(), fixes #3584, references #2919Mike Bayer2015-11-131-2/+2
|/ /
* | - correct the commit from ref #3582 to refer to the correct sub-elementMike Bayer2015-11-111-1/+1
| |
* | - Fixed bug where the "single table inheritance" criteria would beMike Bayer2015-11-112-1/+16
| | | | | | | | | | | | | | added onto the end of a query in some inappropriate situations, such as when querying from an exists() of a single-inheritance subclass. fixes #3582
* | Merge branch ↵Mike Bayer2015-11-101-2/+2
|\ \ | | | | | | | | | 'jeffwidman/update-links-in-sqlalchemy-docs-that-poi-1446667164356' of https://bitbucket.org/jeffwidman/sqlalchemy
| * | Updated PostgreSQL links to point to "current" rather than hardcoded versionJeff Widman2015-11-051-2/+2
| | |
| * | Update links in SQLAlchemy docs that point to postgres docs to use 'devel' ↵Jeff Widman2015-11-041-2/+2
| | | | | | | | | | | | rather than hardcoded version
* | | fix typo: Explcitly -> ExplicitlySven Schliesing2015-11-101-1/+1
|/ /
* | - cross-linking for pool recycle featureMike Bayer2015-10-301-0/+5
| |
* | Merge branch 'pr204'Mike Bayer2015-10-293-3/+26
|\ \
| * | - convert wrap_callable() to a general purpose update_wrapper-likeMike Bayer2015-10-292-13/+9
| | | | | | | | | | | | | | | | | | function; the caller still passes in the "wrapper" - move tests for wrap_callable() to be generic util tests - changelog for pullreq github:204
| * | - wrap ColumnDefault empty arg callables like functools.wraps, setting ↵pr/204Martin J. Hsu2015-10-153-3/+30
| | | | | | | | | | | | __name__, __doc__, and __module__
* | | - add a JSON warning for coerce_compared_valueMike Bayer2015-10-281-0/+20
| | |
* | | - update the pool pessimistic invalidation recipe to refer to theMike Bayer2015-10-221-0/+5
| | | | | | | | | | | | | | | engine_connect event, allowing easy detection of disconnects and full invalidation of the pool
* | | - try to make this language more succinct and fix linksMike Bayer2015-10-201-24/+8
| | | | | | | | | | | | (cherry picked from commit 3ffe8569fbaa72c2d844604b600c4661097339eb)
* | | - adjust 4f54607923a11669961b53f where we still allow_multirow as longMike Bayer2015-10-191-1/+1
| | | | | | | | | | | | as versioning isn't needed, fixes test_unitofworkv2->test_update_multi_missing_broken_multi_rowcount
* | | - Fixed regression in 1.0 where new feature of using "executemany"Mike Bayer2015-10-191-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | for UPDATE statements in the ORM (e.g. :ref:`feature_updatemany`) would break on Postgresql and other RETURNING backends when using server-side version generation schemes, as the server side value is retrieved via RETURNING which is not supported with executemany. fixes #3556
* | | - Added the :paramref:`.AssociationProxy.info` parameter to theMike Bayer2015-10-091-1/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | :class:`.AssociationProxy` constructor, to suit the :attr:`.AssociationProxy.info` accessor that was added in :ticket:`2971`. This is possible because :class:`.AssociationProxy` is constructed explicitly, unlike a hybrid which is constructed implicitly via the decorator syntax. fixes #3551
* | | Merge remote-tracking branch 'origin/pr/203'Mike Bayer2015-10-092-16/+14
|\ \ \
| * | | Remplement Query.one() in terms of .one_or_none()pr/203Eric Siegerman2015-09-282-16/+14
| |/ / | | | | | | Thanks to Mike Bayer for suggesting a simpler refactoring.
* | | Merge remote-tracking branch 'origin/pr/205'Mike Bayer2015-10-091-0/+12
|\ \ \
| * | | Doc fixpr/205Eric Siegerman2015-09-281-0/+12
| |/ /
* | | - open up autoincrement for columns that have a default; autoinc is usuallyMike Bayer2015-10-081-37/+25
| | | | | | | | | | | | "auto" now so True can indicate the dialect would support this
* | | Merge remote-tracking branch 'origin/pr/208'Mike Bayer2015-10-081-1/+1
|\ \ \
| * | | Update base.pypr/208Peter Demin2015-10-071-1/+1
| | | | | | | | | | | | Docstring typo keysowrds => keywords
* | | | - for DB's w/o a real "autoincrement", reflection should be returningMike Bayer2015-10-073-3/+3
|/ / / | | | | | | | | | "auto", doesn't matter if there's a default here
* | | - The system by which a :class:`.Column` considers itself to be anMike Bayer2015-10-076-81/+218
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "auto increment" column has been changed, such that autoincrement is no longer implicitly enabled for a :class:`.Table` that has a composite primary key. In order to accommodate being able to enable autoincrement for a composite PK member column while at the same time maintaining SQLAlchemy's long standing behavior of enabling implicit autoincrement for a single integer primary key, a third state has been added to the :paramref:`.Column.autoincrement` parameter ``"auto"``, which is now the default. fixes #3216 - The MySQL dialect no longer generates an extra "KEY" directive when generating CREATE TABLE DDL for a table using InnoDB with a composite primary key with AUTO_INCREMENT on a column that isn't the first column; to overcome InnoDB's limitation here, the PRIMARY KEY constraint is now generated with the AUTO_INCREMENT column placed first in the list of columns.
* | | - Fixed bug in Oracle dialect where reflection of tables and otherMike Bayer2015-10-051-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | symbols with names quoted to force all-lower-case would not be identified properly in reflection queries. The :class:`.quoted_name` construct is now applied to incoming symbol names that detect as forced into all-lower-case within the "name normalize" process. fixes #3548
* | | - remove ambiguous use of the phrase "joined together by AND" as thisMike Bayer2015-10-011-5/+6
| | | | | | | | | | | | | | | | | | | | | may be construed as the Python "and" keyword - add notes to ORM tutorial for beginners that Python "and" keyword is not to be used fixes #3545
* | | - bzzt, fix the base _post_configure_engine() call to not failMike Bayer2015-09-291-1/+1
| | |
* | | - limit the search for schemas to not include "temp", which is sort of an ↵Mike Bayer2015-09-282-9/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | implicit schema - repair the CREATE INDEX ddl for schemas - update provisioning to include support for setting up ATTACH DATABASE up front for the test_schema; enable "schemas" testing for SQLite - changelog / migration notes for new SQLite schema support - include the "schema" as the "remote_schema" when we reflect SQLite FKs
* | | Merge remote-tracking branch 'origin/pr/198' into pr198Mike Bayer2015-09-281-0/+7
|\ \ \ | |/ / |/| |
View Lorry Controller Status