| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
to use mapper.cascade_iterator() for this purpose as it was not really
designed for that use case. Add docs to cascade_iterator() pointing
to the recipe. fixes #3498
(cherry picked from commit 03797b78475bec9fb9c15f8e926414f3720a273c)
|
| |
|
|
|
|
| |
Fixes #3528
Signed-off-by: Jason Myers <jason@jasonamyers.com>
|
| |
|
|
|
|
|
|
|
| |
column that had some kind of "fetch on update" value and was not
locally present in the given object would cause an AttributeError
within the operation.
fixes #3525
(cherry picked from commit 68a6701c6d72d6c6ef1ea2b7d615273659e8b735)
|
| |
|
|
|
|
| |
detailing ORM event recipes across the board.
(cherry picked from commit 8be93c23ee566de7cefd7d1b8ef044324132a70f)
|
| |
|
|
| |
(cherry picked from commit 6d0c0994e9a08cf5d149af0314970d5f6e25b159)
|
| |
|
|
|
|
|
|
|
|
| |
insert statement, :ticket:`3288`, where the column type for the
default-holding column would not be propagated to the compiled
statement in the case where the default was being used,
leading to bind-level type handlers not being invoked.
fixes #3520
(cherry picked from commit c39ff9978dbb77cbea4f1ee08234887d8aa1b165)
|
| |
|
|
|
|
|
|
| |
where we refer to the "weak_identity_map" option, and add additional
exposition in the session documentation which refers to it.
fixes #3517
(cherry picked from commit 956907a4b15f6dcc492582a7ad03706ff62d96fb)
|
| |
|
|
|
|
|
|
|
| |
all DBs now support ON UPDATE CASCADE other than Oracle, there's no need
to try to reimplement more functionality here and users should be encouraged
to forego natural PKs unless their target platform supports them.
references #2666
(cherry picked from commit d459afa8dbf73b8d9d620d09dede97e3461b6b3f)
|
| |
|
|
|
|
| |
mapper_configured(), after_configured(), and before_configured().
(cherry picked from commit 0127ac668e405584d74c92768a9f0dc7913798fe)
|
| |
|
|
|
|
|
| |
(cherry picked from commit ba1e959e5316a8c17ca80dca950574038bd650c4)
Conflicts:
lib/sqlalchemy/dialects/postgresql/array.py
|
| |
|
|
|
|
|
|
|
| |
- ensure that kwargs can be modified in-place within InstanceEvents.init
and that these take effect for the __init__ method.
- improve documentation for these and related events, including
that kwargs can be modified in-place.
(cherry picked from commit b00b430e87512d721ad30c81fdcb35a5253dfc0a)
|
| |
|
|
|
|
|
|
|
|
|
| |
to function for a many-to-one relationship. The loader used an
API to place "None" into the dictionary which no longer actually
writes a value; this is a side effect of :ticket:`3061`.
- remove InstanceState._initialize() totally, it's used nowhere
else and no longer does what it says it does
- fill in fowards-port version ids throughout the changes for 1.0.9
(cherry picked from commit 5198b1de31029cc985102cd13569086a7056c2f1)
|
| |
|
|
|
|
|
|
|
|
|
| |
without primary keys to be reflected as well as ensured that
a SQL statement involved in foreign key detection is pre-fetched up
front to avoid driver issues upon nested queries. Fixes here
courtesy Eugene Zapolsky; note that we cannot currently test
Sybase to locally verify these changes.
fixes #3508 fixes #3509
(cherry picked from commit a7d7941d3ebafd16f603785c4677e371c675d1c0)
|
| |
|
|
| |
(cherry picked from commit 51870ddaef8abf61ee4c8d6337a72db5395a0a85)
|
| |
|
|
|
| |
`to_unicode` variable was created but was not used.
(cherry picked from commit 69fcabb335130bd0f6e9889c5b191c68192559b5)
|
| |
|
|
| |
(cherry picked from commit 292f5bec1cbfcaa9d16af8fe4149c7191f194f11)
|
| |
|
|
|
|
|
|
|
|
| |
up SQLAlchemy's version detection under Python 3 and inadvertently
not using the correct unicode mode for Python 3. This would cause
issues such as bound variables mis-interpreted as NULL and rows
silently not being returned.
fixes #3491
(cherry picked from commit d8efa2257ec650b345ec6e840984387263a957a6)
|
| |
|
|
| |
(cherry picked from commit 2e52f877638ded9d8440fa94632bff0f1705a83e)
|
| |
|
|
|
|
|
|
|
| |
options and USING of :ticket:`3455` released in 1.0.6,
to disable the feature for Postgresql versions < 8.2 where the
``reloptions`` column is not provided; this allows Amazon Redshift
to again work as it is based on an 8.0.x version of Postgresql.
Fix courtesy Pete Hollobon.
references #3455
|
| |
|
|
|
|
|
|
|
|
|
|
| |
may be called against a stale connection without the "connect"
event handler having been called, in the case where the pool
attempted to reconnect after being invalidated and failed; the stale
connection would remain present and would be used on a subsequent
attempt. This issue has a greater impact in the 1.0 series subsequent
to 1.0.2, as it also delivers a blanked-out ``.info`` dictionary to
the event handler; prior to 1.0.2 the ``.info`` dictionary is still
the previous one.
fixes #3497
|
| |
|
|
|
|
| |
that included non-alphabetic characters in the names, like dots or
spaces, would not be reflected with their name.
fixes #3495
|
| |
|
|
|
|
|
|
|
| |
didn't implement ``__slots__``, and therefore meant all subclasses
of that class didn't either, negating the rationale for ``__slots__``
to be in use. Didn't cause any issue except on IronPython
which apparently does not implement ``__slots__`` behavior compatibly
with cPython.
Fixes #3494
|
| |
|
|
|
| |
- test for .cast() method has no good place now except for
test_cast in test_compiler.py
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
by the ORM :class:`.Query` object (part of the performance
enhancements of :ticket:`3175`) would not raise the "this result
does not return rows" exception in the case where the driver
(typically MySQL) fails to generate cursor.description correctly;
an AttributeError against NoneType would be raised instead.
fixes #3481
|
| | |
| |
| |
| |
| |
| |
| |
| | |
un-adjusted internal symbol names for "anonymous" labels, which
are the "foo_1" types of labels we see generated for SQL functions
without labels and similar. This was a side effect of the
performance enhancements implemented as part of references #918.
fixes #3483
|
| | |
| |
| |
| |
| |
| | |
in conjunction with :func:`.and_` or :func:`.or_` would fail
with an AttributeError.
fixes #3490
|
| | |
| |
| |
| |
| |
| |
| | |
of :class:`.FunctionElement` or other column element that incorrectly
states 'None' or any other invalid object as the ``.type``
attribute will report this exception instead of recursion overflow.
fixes #3485
|
| | |
| |
| |
| | |
(cherry picked from commit 3ef00e816da042d4932be53b86f76db17c800842)
|
| | |
| |
| |
| |
| | |
option for it. keep it local to production of config so values don't
leak in a multi --db situation.
|
| |\ \ |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
- changelog for pullreq github:186
|
| |\ \ \
| |/ /
|/| | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
a column setup on the ABC base which had a different attribute
name vs. column name would not be correctly mapped on the final
base class. The failure on 0.9 would be silent whereas on
1.0 it raised an ArgumentError, so may not have been noticed
prior to 1.0.
fixes #3480
|
| | | |
| | |
| | |
| | |
| | |
| | | |
"multiple parameter sets" there is a much more common case
which works equally well for INSERT/UPDATE/DELETE e.g.
executemany(). reference #3476
|
| | | |
| | |
| | |
| | |
| | |
| | | |
if the name of the attribute being accessed is non-specific,
thereby avoiding collisions on names like items, values, keys.
fixes #3475
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
``__eq__()`` to return a non-boolean-capable object, such as
some geoalchemy types as well as numpy types, were being tested
for ``bool()`` during a unit of work update operation, where in
0.9 the return value of ``__eq__()`` was tested against "is True"
to guard against this.
fixes #3469
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
correctly if it were loaded within the "optimized inheritance load",
which is a special SELECT emitted in the case of joined table
inheritance used to populate expired or unloaded attributes against
a joined table without loading the base table. This is related to
the fact that SQLA 1.0 no longer guesses about loading deferred
columns and must be directed explicitly.
fixes #3468
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
mapped attribute on top of an :func:`.aliased` object would
resolve to the original mapper, not the :func:`.aliased`
version of it, thereby causing problems for a :class:`.Query`
that relies on this attribute (e.g. it's the only representative
attribute given in the constructor) to figure out the correct FROM
clause for the query.
fixes #3466
- apply consitency to ._parententity vs.
__clause_element__()._annotations['parententity']
in terms of aliased class, test it all.
|
| | |
| |
| | |
Fix camelize_classname and pluralize_collection functions as they didn't work as expected.
|