summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* - Postgres: Do not prefix table with schema in: "FOR UPDATE of <table>"pr/216Diana Clarke2015-11-243-3/+19
| | | | | | | | | | | | For example, this query: SELECT s1.users.name FROM s1.users FOR UPDATE OF s1.users should actually be: SELECT s1.users.name FROM s1.users FOR UPDATE OF users fixes #3573
* - add py35Mike Bayer2015-11-221-1/+1
|
* - set explicit encoding settings for default mysql driverMike Bayer2015-11-211-1/+1
|
* - Fixed joinedload bug which would occur when a. the query includesMike Bayer2015-11-213-3/+126
| | | | | | | | | | | | 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
* - don't create tables on compile-only testsMike Bayer2015-11-211-0/+2
|
* - try to get this to skip for oracleMike Bayer2015-11-201-1/+4
|
* - A rare case which occurs when a :meth:`.Session.rollback` fails in theMike Bayer2015-11-194-3/+55
| | | | | | | | | | | | 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
* - add documentation that describes, then proceeds to warn aboutMike Bayer2015-11-191-0/+44
| | | | | | | | | | the many caveats and confusing effects of, the popular approach of using contains_eager() to alter the natural result of a related collection. I'm not a fan of this technique as it changes the semantics of a relationship in such a way that the rest of the ORM isn't aware of and it also can be undone very easily; hence the section needs as much text for warnings as for describing the technique itself. fixes #3563
* - Fixed the ``.python_type`` attribute of :class:`.postgresql.INTERVAL`Mike Bayer2015-11-193-0/+34
| | | | | | | | | 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-193-7/+75
| | | | | | | 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-183-5/+39
| | | | | | 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-143-3/+102
| | | | | | 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-142-1/+3
|\
| * Pass precision value to mssql.DATETIME2 when it is 0pr/213Jacobo de Vera2015-11-132-1/+3
| | | | | | | | | | 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-132-3/+17
|/
* - 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-115-2/+82
| | | | | | | 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
* | Merge branch 'jeffwidman/fix-typo-foriegn-foreign-1446862160653' of ↵Mike Bayer2015-11-101-1/+1
|\ \ | | | | | | | | | https://bitbucket.org/jeffwidman/sqlalchemy-1 into typos
| * | Fix typo: foriegn --> foreignJeff Widman2015-11-071-1/+1
| |/
* | fix typo: Explcitly -> ExplicitlySven Schliesing2015-11-101-1/+1
| |
* | - fix ambiguous documentation re: after_flush_postexec(), theMike Bayer2015-11-091-1/+4
| | | | | | | | looping nature of it only occurs within the context of a commit.
* | - fix broken link to loader behaviorMike Bayer2015-11-071-1/+1
|/
* - cross-linking for pool recycle featureMike Bayer2015-10-302-0/+7
|
* Merge branch 'pr204'Mike Bayer2015-10-296-3/+106
|\
| * - convert wrap_callable() to a general purpose update_wrapper-likeMike Bayer2015-10-295-73/+88
| | | | | | | | | | | | 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-154-3/+91
| | | | | | | | __name__, __doc__, and __module__
* | - add a JSON warning for coerce_compared_valueMike Bayer2015-10-281-0/+20
| |
* | Merge remote-tracking branch 'origin/pr/196' into pr196pr196Mike Bayer2015-10-221-1/+1
|\ \
| * | Link to maintained redshift dialectpr/196Thomas Grainger2015-08-191-1/+1
| | |
* | | - update the pool pessimistic invalidation recipe to refer to theMike Bayer2015-10-222-38/+62
| | | | | | | | | | | | | | | engine_connect event, allowing easy detection of disconnects and full invalidation of the pool
* | | - release date for 1.0.9Mike Bayer2015-10-201-0/+1
| | |
* | | - try to make this language more succinct and fix linksMike Bayer2015-10-201-24/+8
| | | | | | | | | | | | (cherry picked from commit 3ffe8569fbaa72c2d844604b600c4661097339eb)
* | | - use is_() here to more clearly show what's going wrongMike Bayer2015-10-191-13/+25
| | | | | | | | | | | | on occasional pypy test runs
* | | - 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-193-1/+101
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | - exclude this from unpredictable gcMike Bayer2015-10-111-1/+1
| | |
* | | - modernize some very old global-engine tests w/ bad teardownsMike Bayer2015-10-111-238/+260
| | |
* | | - repair flake8 issuesMike Bayer2015-10-111-44/+49
| | |
* | | - repair laziness about setting time zone here, which is leakingMike Bayer2015-10-111-9/+17
| | | | | | | | | | | | out depending on connection pool state
* | | - Added the :paramref:`.AssociationProxy.info` parameter to theMike Bayer2015-10-094-1/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | :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-094-19/+22
|\ \ \
| * | | Remplement Query.one() in terms of .one_or_none()pr/203Eric Siegerman2015-09-284-19/+22
| | |/ | |/| | | | Thanks to Mike Bayer for suggesting a simpler refactoring.
* | | - this was supposed to be client-side SQL default not server sideMike Bayer2015-10-091-1/+1
| | |
* | | 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-084-49/+52
| | | | | | | | | | | | "auto" now so True can indicate the dialect would support this
* | | Merge remote-tracking branch 'origin/pr/208'Mike Bayer2015-10-081-1/+1
|\ \ \
View Lorry Controller Status