| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
usable without the full plugin_base setup.
- move some Python-env requirements to the importable
requirements.py module.
Change-Id: I3bfffce75b53040f6923b89e0fa2140bec243bc8
|
|
|
|
| |
Change-Id: I12a84e00169e2a15582e814901ecd207066934c8
|
|
|
|
| |
Change-Id: I55de02d9421a3da7b17e24de6fdcaf5daacbba4f
|
|
|
|
|
|
|
|
| |
pre-loading of _ConnectionRecord objects
- ensure _ConnectionRecord.close() leaves the record in a good
state for reopening
Change-Id: I4eeb8e29f643950afb9eaab94d815e2a115db3d6
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Stringify of expression with unnamed :class:`.Column` objects, as
occurs in lots of situations including ORM error reporting,
will now render the name in string context as "<name unknown>"
rather than raising a compile error.
Change-Id: I76f637c5eb4cfdb1b526964cb001565b97e296da
Fixes: #3789
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixed bug where the "simple many-to-one" condition that allows lazy
loading to use get() from identity map would fail to be invoked if the
primaryjoin of the relationship had multiple clauses separated by AND
which were not in the same order as that of the primary key columns
being compared in each clause. This ordering
difference occurs for a composite foreign key where the table-bound
columns on the referencing side were not in the same order in the .c
collection as the primary key columns on the referenced side....which
in turn occurs a lot if one is using declarative mixins and/or
declared_attr to set up columns.
Change-Id: I66cce74f614c04ed693dc0d58ac8c952b2f8ae54
Fixes: #3788
|
|
|
|
| |
Change-Id: I5d3f74c002f9d4593940ab4d68a3b35f3f227597
|
|
|
|
|
|
|
|
|
|
|
| |
Added support for parsing MySQL/Connector boolean and integer
arguments within the URL query string: connection_timeout,
connect_timeout, pool_size, get_warnings,
raise_on_warnings, raw, consume_results, ssl_verify_cert, force_ipv6,
pool_reset_session, compress, allow_local_infile, use_pure.
Change-Id: I2a1a17d13d47d56871bff32e94fdbed8bc003ad7
Fixes: #3787
|
|
|
|
|
|
|
|
|
|
| |
Raise a more descriptive exception / message when ClauseElement
or non-SQLAlchemy objects that are not "executable" are erroneously
passed to ``.execute()``; a new exception ObjectNotExecutableError
is raised consistently in all cases.
Change-Id: I2dd393121e2c7e5b6b9e40286a2f25670876e8e4
Fixes: #3786
|
|
|
|
| |
This example doesn't work with 'back_populates' because 'parent_associations' and 'child_associations' are not defined in Parent and Child classes respectively.
Alternatively, we could create 'parent_associations' and 'child_associations' into the classes.
|
|\ |
|
| | |
|
|\ \ |
|
| |/ |
|
|/
|
|
| |
replacing it with more concrete and working example.
|
|
|
|
|
|
|
|
| |
Two @validates decorators that make use of the same name
is not supported. Raise an exception.
Change-Id: Ia3e89ffdc9ef345a0de258e2ac0ac5e0bd421c61
Fixes: #3776
|
|\ |
|
| |
| |
| |
| |
| | |
Change-Id: I5ad44362515908592f1e8b1e6254a5270d43234a
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/295
|
| |
| |
| |
| | |
Change-Id: I36fbbfd1223ef5298c679f46db24e1bf3013cef0
|
|\ \ |
|
| |/ |
|
|\ \ |
|
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The approach here is still error prone
and hard to follow. Reorganize the whole
thing to take a pretty blunt approach to
the structure of to_join(). Also fix some never-called
code (!) in _prep_for_joins() and ensure we re-use
an aliased object.
Fixes: #3774
Change-Id: Ie6319415ae7213b4a33eac2ab70803ad2880d340
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixed bug in subquery eager loading where a subqueryload
of an "of_type()" object linked to a second subqueryload of a plain
mapped class would fail to link the joins correctly.
Change-Id: I4be89e6f5e492438464a2ded01eb9c84d7ff7d4e
Fixes: #3773
|
|/ /
| |
| |
| | |
Change-Id: I8d44b90bb9d05275de19d3ce2d9124050add5f01
|
| |
| |
| |
| |
| |
| | |
polymorphically
Change-Id: Id82435fa16b0456f32bce49715c6606e3a1534c8
|
| |
| |
| |
| |
| | |
Change-Id: I87918ab4cd294d4b4a87a377c7b6b21105f4fd55
(cherry picked from commit 68b6984912760bfe4d9270750d8f39b9036b65b5)
|
|/
|
|
|
|
| |
loading documentation
Change-Id: I3ce7e2cc521c4dd155195819a919017d4cc63b3c
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixed regression in JSON datatypes where the "literal processor" for
a JSON index value, that needs to take effect for example within DDL,
would not be invoked for the value. The native String and Integer
datatypes are now called upon from within the JSONIndexType
and JSONPathType. This is applied to the generic, Postgresql, and
MySQL JSON types.
Change-Id: Ifa5f2acfeee57a79d01d7fc85d265a37bd27c716
Fixes: #3765
|
|
|
|
|
| |
Change-Id: I23a6abb26bbbe3d118887d043ce761fc4572d8d2
Fixes: #3766
|
|
|
|
|
|
|
|
|
|
| |
Users who pass many different object types to bulk_save_objects
may be surprised that the INSERT/UPDATE batches must necessarily
be broken up by type. Add this to the list of caveats.
Co-authored-by: Mike Bayer
Change-Id: I8390c1c971ced50c41268b479a9dcd09c695b135
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/294
|
|\ |
|
| | |
|
|\ \
| | |
| | |
| | | |
https://bitbucket.org/michaelwilliamson/sqlalchemy
|
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The change in Index for 1.1 combined with the fix for
ref #3763 still fails to deliver the correct object
resolved by __clause_element__() to the list of expressions
for compilation. Make sure we use the expression that's
been unwrapped from __clause_element__().
Change-Id: Ie1df8db5090de665048331786f0024d52851923f
Fixes: #3763
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixed bug where :class:`.Index` would fail to extract columns from
compound SQL expressions if those SQL expressions were wrapped inside
of an ORM-style ``__clause_element__()`` construct. This bug
exists in 1.0.x as well, however in 1.1 is more noticeable as
hybrid_property @expression now returns a wrapped element.
Fixes: #3763
Change-Id: I992536386503a1fb3f2305790abe008d72c44c4a
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It wasn't clear how this differs from order_by(None);
add more tests and document that this has to do with whether or
not mapper.order_by will be re-enabled as well.
Change-Id: I332e8ac60c999b38c5a243f1cb72de3cf77891b6
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
and test/sql/test_metadata IndexTest into
test/sql/test_metadata ConstraintTest
Change-Id: I7aeee9a1edbbd889200afc393695f73d5fbac3f3
|
|\ \ \
| |/ / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This replicates the same behavior as order_by().
order_by() will also be updated to deprecate passing
of False as this is no longer functionally different
than passing None.
Change-Id: I2fc05d0317d28b6c83373769a48f7eea32d56290
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/297
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
PyMySQL upstream has released 0.7.6 which should resolve
JSON encoding issues.
Change-Id: Icf543d48dace1419a0aac78bdb15ec666f0edafe
Fixes: #3754
|
|/ /
| |
| |
| | |
Change-Id: I1d8ac48e6457e80e93b925152f434c13139b3d94
|
| |
| |
| |
| |
| |
| | |
Fixes #3760
Change-Id: I0613eb66bfdc9d7118688c74e29c8da322c3b4db
|