| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
Fix very minor typo
|
| |
|
|
| |
(cherry picked from commit b1c9b3bd384fc40e1c411abef12eaf04b574612f)
|
| |
|
|
| |
(cherry picked from commit 9bdbf19d54174c1077689bc472dc088c9b06aa24)
|
| |
|
|
|
|
|
|
|
| |
be properly typed as boolean in the result, and also would fail to be
anonymously aliased in a SELECT list as is the case with a
non-negated EXISTS construct.
fixes #3682
(cherry picked from commit 07a4b6cbcda6e6ee6e67893c5a5d2fd01e5f125f)
|
| |
|
|
| |
(cherry picked from commit 732c613eeb890e7b7cbd04750468dac584151a31)
|
| |
|
|
| |
(cherry picked from commit f61194cb865db8b29cc65e47782bb72e54b14ada)
|
| |
|
|
| |
(cherry picked from commit 3d83e1639e1325af67d2bba390bd7c40838380b9)
|
| |
|
|
|
|
|
|
|
|
|
| |
passed to :func:`.column_property`, so that if the same attribute
is referred to as a column expression twice the names are de-duped,
thus avoiding "ambiguous column" errors. Previously, the
``.label(None)`` would need to be applied in order for the name
to be de-anonymized.
fixes #3663
(cherry picked from commit 0210695bd97e76f58d8781b69337816501482fb0)
|
| |
|
|
|
|
|
|
|
| |
would be turned into a list of individual characters. This would
impact among other things using the :meth:`.Query.get` method
on a primary key that's a bytes object.
fixes #3660
(cherry picked from commit 01809bddff5b6e93010eb139aed54526c6e6c058)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
handled within visit_select(); this attribute was added in the
1.0 series to accommodate the subquery wrapping behavior of
SQL Server and Oracle while also working with positional
column targeting and no longer relying upon "key fallback"
in order to target columns in such a statement. The IBM DB2
third-party dialect also has this use case, but its implementation
is using regular expressions to rewrite the textual SELECT only
and does not make use of a "wrapped" select at this time.
The logic no longer attempts to reconcile proxy set collections as
this was not deterministic, and instead assumes that the select()
and the wrapper select() match their columns postionally,
at least for the column positions they have in common,
so it is now very simple and safe. fixes #3657.
- as a side effect of #3657 it was also revealed that the
strategy of calling upon a ResultProxy._getter was not
correctly calling into NoSuchColumnError when an expected
column was not present, and instead returned None up to
loading.instances() to produce NoneType failures; added
a raiseerr argument to _getter() which is called when we
aren't expecting None, fixes #3658.
(cherry picked from commit 8ad968f33100baeb3b13c7e0b724b6b79ab4277f)
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
primary key that has values for some but not all of the PK fields
would emit a SELECT statement leaking the internal NEVER_SET symbol
into the query, rather than detecting that this object does not have
a searchable primary key and no SELECT should be emitted.
fixes #3647
(cherry picked from commit 366f97b5617af0d15cfaf594ec5ef0408c70e873)
|
| |
|
|
|
|
|
|
| |
expression would not escape properly, e.g. ``some\:\:expr``, as is most
commonly required when rendering Postgresql-style CAST expressions.
fixes #3644
(cherry picked from commit 29dcaa2b0ae2d26b36ec624be80f56e03ab9095e)
|
| |
|
|
|
|
|
|
|
|
|
| |
- establish make_transient and make_transient_to_detached as special-use,
advanced use only functions
- list all conditions under make_transient() under which an attribute
will not be loaded and establish that make_transient() does not attempt
to load all attributes before detaching the object from its
session, fixes #3640
(cherry picked from commit 7eff4e8f3e3999d9eb914647d8776e6e5b7ee88e)
|
| |
|
|
|
|
|
| |
- move tests to CRUDTest
- changelog, fixes #3643
(cherry picked from commit 150591f9e0a94902cb2a76b68ac7c9d8a1a3ec83)
|
| |
|
|
| |
(cherry picked from commit 9149fd062b8b5f4d84902b4581288ab991fd25ce)
|
| |
|
|
|
|
|
|
|
|
|
| |
override with a column expression (e.g. by using ``'x' in col``)
would cause an endless loop in the case of an ARRAY type, as Python
defers this to ``__getitem__`` access which never raises for this
type. Overall, all use of ``__contains__`` now raises
NotImplementedError.
fixes #3642
(cherry picked from commit e0a580b3d055a600afae61840058a5a30ef5fe74)
|
| |
|
|
| |
(cherry picked from commit 859379e2fcc4506d036700ba1eca4c0ae526a8ee)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the warning here to all safe_reraise() cases in Python 2.
- Revisiting :ticket:`2696`, first released in 1.0.10, which attempts to
work around Python 2's lack of exception context reporting by emitting
a warning for an exception that was interrupted by a second exception
when attempting to roll back the already-failed transaction; this
issue continues to occur for MySQL backends in conjunction with a
savepoint that gets unexpectedly lost, which then causes a
"no such savepoint" error when the rollback is attempted, obscuring
what the original condition was.
The approach has been generalized to the Core "safe
reraise" function which takes place across the ORM and Core in any
place that a transaction is being rolled back in response to an error
which occurred trying to commit, including the context managers
provided by :class:`.Session` and :class:`.Connection`, and taking
place for operations such as a failure on "RELEASE SAVEPOINT".
Previously, the fix was only in place for a specific path within
the ORM flush/commit process; it now takes place for all transational
context managers as well.
fixes #2696
(cherry picked from commit 8a1e619fb20df1be6ad2e0c563e451e17eb17628)
|
| |
|
|
| |
(cherry picked from commit 4b9f6f407ceedde247982501a6ae406242c80b4a)
|
| |
|
|
| |
(cherry picked from commit 324e532d6081d9b9ea90bf3945cecfc792264f8d)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
need this collection except in the extend/update uses where we
create it ad-hoc. simplifies pickling. Compatibility with 1.0
should be OK as ColumnColleciton uses __getstate__ in any case
and the __setstate__ contract hasn't changed.
- Fixed bug in :class:`.Table` metadata construct which appeared
around the 0.9 series where adding columns to a :class:`.Table`
that was unpickled would fail to correctly establish the
:class:`.Column` within the 'c' collection, leading to issues in
areas such as ORM configuration. This could impact use cases such
as ``extend_existing`` and others. fixes #3632
(cherry picked from commit 8163de4cc9e01460d3476b9fb3ed14a5b3e70bae)
|
| |
|
|
|
|
| |
references #3638
(cherry picked from commit 67a69da3aa86c8b2b560ed79a9c91408ad704879)
|
| |
|
|
|
|
|
|
|
|
|
| |
that have problems with right-nested joins and UNION column keys;
references #3633 references #3634. backport from 1.1 to 0.9
announcing 1.1 as where these behaviors will be retired based
on version-specific checks
- fix test_resultset so that it passes when SQLite 3.10.0 is
present, references #3633
(cherry picked from commit 89fa08792e98b9e31452aa3c949d9b909b10e7cd)
|
| |
|
|
|
|
| |
create confusion for inherited classes such as BYTEA, fixes
(cherry picked from commit 47d8858c54401cdf10285b7935049faf87432f55)
|
| |
|
|
|
|
|
| |
- remove redundant concrete helper docs from declarative docs,
two places is enough
(cherry picked from commit a53bd6f74b4f41fd04c8cde1f8b58bbb766fe18d)
|
| |
|
|
| |
(cherry picked from commit b53667526eb9b2fabccfb097a5b76906d6452249)
|
| |
|
|
|
|
| |
favor declarative, fixes #2890
(cherry picked from commit 632c4f21fa3cab353b801f585183494c529c6896)
|
| |
|
|
| |
(cherry picked from commit 02271efd8976154f855646478b5438db078f7101)
|
| |
|
|
|
|
|
|
|
|
| |
the exception to itself as the "cause"; while the Python 3 interpreter
is OK with this, it could cause endless loops in iPython.
fixes #3625
- add tests for reraise, raise_from_cause
- raise_from_cause is the same on py2k/3k, use just one function
(cherry picked from commit d4d9a6524886eb33644e8ce42212267fa569e555)
|
| |
|
|
| |
(cherry picked from commit f9b21855861c1c8983acc934fe47546d71a1df05)
|
| |
|
|
| |
(cherry picked from commit 66560cef7457d69f56cd2ca3bab93cb033a61a84)
|
| |
|
|
|
|
|
| |
unfortunately we can't show the SQL unless we filtered it out
from doctest...not worth it
(cherry picked from commit 7bb578b1bd61ec9a2506d1bdb60bb28579204808)
|
| |
|
|
|
|
|
| |
(cherry picked from commit c4f415d97988bc8a8d901b150bfb67571f29712e)
- changelog for pr bitbucket:70, fixes #3624
(cherry picked from commit 215167d8d38a381d27c8448f5c6e50c70b9ba0cc)
|
| |
|
|
|
|
|
|
| |
- fix "version" got whacked into "f" in core tutorial
- fix short underline in automap
- fix unmatched boldface in session events
(cherry picked from commit d03477d4b761132f44c48417be09d622ad9adfd3)
|
| |
|
|
| |
(cherry picked from commit 56b76ce7a823a076bd91490f940df95ad409db61)
|
| |
|
|
| |
(cherry picked from commit bb294497558f96c92253a4a68129a7c7984d3af9)
|
| |
|
|
|
|
|
|
|
| |
system failed to accommodate for multiple :func:`.undefer_group`
loader options in a single query. Multiple :func:`.undefer_group`
options will now be taken into account even against the same
entity. fixes #3623
(cherry picked from commit c7ae0daf0ed24e2697d6f948db2d9fdc5953c795)
|
| |
|
|
|
|
|
| |
only when a 1.1.x is released would we want to capture what's still
sitting in a 1.0.x changelog
(cherry picked from commit 16746dd1a63198e3c27422517fa22ec76f441ceb)
|
| |
|
|
|
|
|
|
|
|
| |
no longer called for an UPDATE or DELETE statement emitted via plain
text or via the :func:`.text` construct, affecting those drivers
that erase cursor.rowcount once the cursor is closed such as SQL
Server ODBC and Firebird drivers.
fixes #3622
(cherry picked from commit 197ffa2be2cadce3df8bfb0799b3c80158250286)
|
| | |
|
| |
|
|
|
|
|
|
|
| |
such that we no longer assume the "ALGORITHM" keyword is present in
the reflected view source, as some users have reported this not being
present in some Amazon RDS environments.
fixes #3613
(cherry picked from commit 8c54b14b5c0feee41bd9b9032f6b17b2dbd560a9)
|
| |
|
|
| |
(cherry picked from commit 5c7ade2f4218b55db8f758949b82a3414474aeb2)
|
| |
|
|
|
|
|
| |
where the "default" argument was not included.
fixes #3605
(cherry picked from commit 913858c949ae9ca6250217d82d72c7d79e9f6585)
|
| |
|
|
| |
(cherry picked from commit 30be49c157e6ebe47c32abb98a570a013418b1e6)
|
| |
|
|
| |
(cherry picked from commit 738d515b95f1ff94d7dfd265883237d247d1c153)
|
| |
|
|
|
|
|
|
|
|
| |
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 a22b2085068f860d05dbb98631d2ac2079a12b39)
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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
(cherry picked from commit a8ec3491983ed5e68452514b4d52a4347377809f)
|
| |
|
|
|
| |
remove "undoc members" that was putting some random server_default
atributes from ColumnClause
|