summaryrefslogtreecommitdiff
path: root/lib
Commit message (Collapse)AuthorAgeFilesLines
* fix some typospr/220Nils Philippsen2015-12-082-2/+2
|
* - Fixed bug in MySQL reflection where the "fractional sections portion"Mike Bayer2015-12-071-0/+5
| | | | | | | | of the :class:`.mysql.DATETIME`, :class:`.mysql.TIMESTAMP` and :class:`.mysql.TIME` types would be incorrectly placed into the ``timestamp`` attribute, which is unused by MySQL, instead of the ``fsp`` attribute. fixes #3602
* - write a real inline documentation section for from_self(),Mike Bayer2015-12-071-2/+163
| | | | | building on the example of query.join(). Ideally all the methods in Query would have this kind of thing. fixes #3544
* - fix loading.py merge_result for new _merge() argumentMike Bayer2015-12-041-2/+2
|
* - The :meth:`.Session.merge` method now tracks pending objects byMike Bayer2015-12-044-10/+28
| | | | | | | | primary key before emitting an INSERT, and merges distinct objects with duplicate primary keys together as they are encountered, which is essentially semi-deterministic at best. This behavior matches what happens already with persistent objects. fixes #3601
* - Fixed issue where post_update on a many-to-one relationship wouldMike Bayer2015-12-021-3/+5
| | | | | | fail to emit an UPDATE in the case where the attribute were set to None and not previously loaded. fixes #3599
* - Fixed bug where CREATE TABLE with a no-column table, but a constraintMike Bayer2015-12-011-1/+1
| | | | | | | such as a CHECK constraint would render an erroneous comma in the definition; this scenario can occur such as with a Postgresql INHERITS table that has no columns of its own. fixes #3598
* - Added the error "20006: Write to the server failed" to the listMike Bayer2015-11-301-1/+2
| | | | | | of disconnect errors for the pymssql driver, as this has been observed to render a connection unusable. fixes #3585
* Merge remote-tracking branch 'origin/pr/216'Mike Bayer2015-11-302-3/+3
|\
| * - Postgres: Do not prefix table with schema in: "FOR UPDATE of <table>"pr/216Diana Clarke2015-11-242-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | 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
* | Merge remote-tracking branch 'origin/pr/215'Mike Bayer2015-11-301-1/+1
|\ \
| * | fix postgresql exclude contraint to check when= against None rather than ↵pr/215aisch2015-11-231-1/+1
| |/ | | | | | | __bool__ eval
* | Merge remote-tracking branch 'origin/pr/212'Mike Bayer2015-11-301-1/+2
|\ \
| * | py2k: accept unicode literals on :func:`backref`, toopr/212Nils Philippsen2015-11-251-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | Fixed bug where in Py2K a unicode literal would not be accepted as the string name of a class or other argument within declarative using :func:`.backref` on :func:`.relationship`. amends commit e6f67f48054d906856f879bc1803ea639aa4b670
* | | Merge remote-tracking branch 'origin/pr/211'Mike Bayer2015-11-302-3/+3
|\ \ \
| * | | Change generator termination from StopIteration to return.pr/211pgjones2015-10-302-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From [PEP 479](https://www.python.org/dev/peps/pep-0479/) the correct way to terminate a generator is to return (which implicitly raises StopIteration) rather than raise StopIteration. Without this change using sqlalchemy in python 3.5 or greater results in these warnings PendingDeprecationWarning: generator '__iter__' raised StopIteration which this commit should remove.
* | | | - A descriptive ValueError is now raised in the event that SQL serverMike Bayer2015-11-301-2/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | returns an invalid date or time format from a DATE or TIME column, rather than failing with a NoneType error. Pull request courtesy Ed Avis. pullreq github:206
* | | | Merge remote-tracking branch 'origin/pr/218'Mike Bayer2015-11-302-1/+2
|\ \ \ \
| * | | | Fix _assert_unorderable_types on py36.pr/218Iuri de Silvio2015-11-302-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The error message changed to: `'<' not supported between instances of 'foo' and 'bar'`
* | | | | Merge remote-tracking branch 'origin/pr/210'Mike Bayer2015-11-304-7/+10
|\ \ \ \ \ | |/ / / / |/| | | |
| * | | | Update usages of getargspec to compat version.pr/210Jacob MacDonald2015-10-294-7/+10
| |/ / / | | | | | | | | | | | | | | | | The places inspect.getargspec was being used were causing problems for newer Python versions.
* | | | - Fixed an issue in baked queries where the .get() method, used eitherMike Bayer2015-11-291-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | directly or within lazy loads, didn't consider the mapper's "get clause" as part of the cache key, causing bound parameter mismatches if the clause got re-generated. This clause is cached by mappers on the fly but in highly concurrent scenarios may be generated more than once when first accessed. fixes #3597
* | | | - Added support for parameter-ordered SET clauses in an UPDATEMike Bayer2015-11-285-68/+134
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | statement. This feature is available by passing the :paramref:`~.sqlalchemy.sql.expression.update.preserve_parameter_order` flag either to the core :class:`.Update` construct or alternatively adding it to the :paramref:`.Query.update.update_args` dictionary at the ORM-level, also passing the parameters themselves as a list of 2-tuples. Thanks to Gorka Eguileor for implementation and tests. adapted from pullreq github:200
* | | | - 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
View Lorry Controller Status