| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
for setting up baked lazy loaders would interfere with other
loader strategies that rely on lazy loading as a fallback, e.g.
joined and subquery eager loaders, leading to ``IndexError``
exceptions at mapper configuration time.
fixes #3612
|
| | |
| |
| |
| | |
(cherry picked from commit 9f6f34bc8f04e30115e047d78b9db96995bdb898)
|
| | |
| |
| |
| |
| |
| |
| | |
the check added for a polymorphic joinedload from a
poly_subclass->class->poly_baseclass connection would fail for the
scenario of class->poly_subclass->class.
fixes #3611
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
remove "undoc members" that was putting some random server_default
atributes from ColumnClause
(cherry picked from commit 270301890ae87ec32a46bb17889d9776b7de1468)
|
| | |
| |
| |
| |
| |
| | |
the same cached starting statement each time. no issue has been observed
with the former but it could perhaps have issues w/ versioning
or eager_defaults
|
| | |
| |
| |
| |
| |
| |
| |
| | |
would not bump a version id counter when in use. The experience
here is still a little rough as the original version id is required
in the given dictionaries and there's not clean error reporting
on that yet.
fixes #3610
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
insert-default holding columns not otherwise included in the SET
clause (such as primary key cols) to get rendered into the RETURNING
even though this is an UPDATE.
- Major fixes to the :paramref:`.Mapper.eager_defaults` flag, this
flag would not be honored correctly in the case that multiple
UPDATE statements were to be emitted, either as part of a flush
or a bulk update operation. Additionally, RETURNING
would be emitted unnecessarily within update statements.
fixes #3609
|
| | |
| |
| |
| |
| |
| | |
cause a subsequent call to the :meth:`.Query.with_parent` method to
fail. fixes #3606
- add mark-as-fail test for #3607
|
| | |
| |
| |
| | |
(cherry picked from commit 6b87e0b301f123359f8a32114a3e888d6dd05bfc)
|
| | |
| |
| |
| |
| | |
to the :class:`.mutable.MutableDict` class.
fixes #3605
|
| | |
| |
| |
| |
| | |
back_populates while still maintaining great familiarity
w/ backref so as not to confuse people. fixes #3390
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
are now exercised within the normal unit test suite in both Python
2 and Python 3.
- remove the old testdocs.py runner and replace with test/base/test_tutorials.py
- use pytest's unicode fixer so that we can test for unicode strings
in both py2k/3k
- use py3k format overall for prints, exceptions
- add other fixers to guarantee deterministic results
- add skips and ellipses to outputs that aren't worth matching
|
| | |\ |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Includes removal of adapt_like_to_iterable() as well
as _set_iterable(), uses __slots__ for collectionadapter,
does much less duck typing of collections.
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
the :class:`.Select` construct would have its ``._raw_columns``
collection mutated in-place when compiling the :class:`.Insert`
construct, when the target :class:`.Table` has Python-side defaults.
The :class:`.Select` construct would compile standalone with the
erroneous column present subsequent to compilation of the
:class:`.Insert`, and the the :class:`.Insert` statement itself would
fail on a second compile attempt due to duplicate bound parameters.
fixes #3603
|
| | |
| |
| |
| |
| |
| | |
- add version switch for backend fsp test
(cherry picked from commit 67b22cee3ab2c17b61100f1ccd69081082c0f074)
|
| | |
| |
| |
| | |
an issue with just one test
|
| | |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| |
| |
| | |
individual categories w/ modernized fixtures, assert attributes
within type objects.
|
| | |
| |
| |
| |
| | |
building on the example of query.join(). Ideally all the methods
in Query would have this kind of thing. fixes #3544
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| |
| |
| |
| | |
fail to emit an UPDATE in the case where the attribute were set to
None and not previously loaded.
fixes #3599
|
| | |
| |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| |
| |
| |
| | |
of disconnect errors for the pymssql driver, as this has been observed
to render a connection unusable.
fixes #3585
|
| | | |
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | | | |
|
| | |\ \ |
|
| | | |/
| | |
| | |
| | | |
__bool__ eval
|
| | |\ \ |
|
| | | | | |
|
| | |\ \ \ |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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
backport to rel_1_0
(cherry picked from commit 58f73d2278393d813c7f39736fc96c5086f18f6d)
(cherry picked from commit 33c3aded3a1944d93e9e6bca53e2f749980b8b09)
|
| | |\ \ \ \ |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
(cherry picked from commit 4bb6770ae872b69bd65ba0d67a7e1453d1a4e14b)
|
| | |\ \ \ \ \ |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
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.
|