| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
exactly
|
|
|
|
|
|
|
|
| |
to not be loaded, if the joined eager load were from a row where the
same entity were present multiple times, some calling for the attribute
to be eagerly loaded and others not. The logic here is revised to
take in the attribute even though a different loader path has
handled the parent entity already. fixes #3431
|
|
|
|
|
| |
for example an exception object made within a test suite can
still repr (error seen in Keystone)
|
| |
|
|
|
|
|
|
|
|
|
| |
logging, exception, and ``repr()`` purposes now truncate very large
scalar values within each collection, including an
"N characters truncated"
notation, similar to how the display for large multiple-parameter sets
are themselves truncated.
fixes #2837
|
|
|
|
| |
to the new MutableList and MutableSet classes, fixes #3297
|
|\ |
|
| |
| |
| |
| | |
from https://bitbucket.org/zzzeek/sqlalchemy/issues/3297
|
| | |
|
|/
|
|
| |
here, fixes #3652
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
INSERT, UPDATE, and DELETE statements to both specify their own
WITH clause, as well as for these statements themselves to be
CTE expressions when they include a RETURNING clause.
fixes #2551
|
|
|
|
|
|
| |
that this structure is only intended to track additions
and removals from the dictionary, not recursive tracking
of embedded changes. fixes #3646.
|
|
|
|
|
| |
because we never log in on the ts1/ts2. races against other runs
and erases their DBs
|
|
|
|
|
|
| |
expression would not escape properly, e.g. ``some\:\:expr``, as is most
commonly required when rendering Postgresql-style CAST expressions.
fixes #3644
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
:meth:`.Query.distinct` is combined with :meth:`.Query.order_by` such
that columns which are already present will not be added
a second time, even if they are labeled with a different name.
Regardless of this change, the extra columns added to the SQL have
never been returned in the final result, so this change only impacts
the string form of the statement as well as its behavior when used in
a Core execution context. Additionally, columns are no longer added
when the DISTINCT ON format is used, provided the query is not
wrapped inside a subquery due to joined eager loading.
fixes #3641
|
| |
|
|
|
|
|
|
|
|
| |
connections at all,
yet cx_Oracle still has open sessions that cannot be killed until process dies.
Oracle wins! Add a completely separate DB reaper script that runs
after py.test is done.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
- 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
|
| |
|
| |
|
| |
|
|
|
|
| |
--backend-only
|
|
|
|
| |
if not
|
|
|
|
| |
same time
|
|
|
|
|
|
| |
unfortunately the synonym doesn't work for SQL statements here
when the dblink is on a different user, testing this is not really
critical so just removed it.
|
| |
|
|
|
|
|
|
|
| |
on unicode. Enum would be better as a TypeDecorator
at this point but then that becomes awkward with native enum
types (Interval works that way, but we don't need the bind_processor for
native interval...)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
- move tests to CRUDTest
- changelog, fixes #3643
|
| |
|
| |
|
|\ |
|
| |\ |
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | | |
(pull request #1)
Removed entry that causes AttributeError (#3621) - Oracle zxJDBC fails with AttributeError in object OracleCompiler_zxjdbc
|
| |/ /
| | |
| | |
| | | |
AttributeError in object OracleCompiler_zxjdbc
|
| | |
| | |
| | |
| | | |
- modernize those tests as well
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
fixes #3095, #3292
- reorganize enum constructor to again work with the MySQL
ENUM type
- add a new create_constraint flag to Enum to complement that of
Boolean
- reinstate the CHECK constraint tests for enum, these already
fail /skip against the MySQL backend
- simplify lookup rules in Enum, have them apply to all varieties
of Enum equally
|
| | |
| | |
| | |
| | | |
within the Enum type.
|
| | |
| | |
| | |
| | |
| | | |
I'm using and many of these seem contradictory and/or undesirable.
block all until individual rules can be approved.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | |
| | |
| | |
| | | |
on database use
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
removed; this has emitted a warning for many years and projects
should be calling upon ``sqlalchemy.dialects.postgresql``.
Engine URLs of the form ``postgres://`` will still continue to function,
however.
|
| | | |
|