| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
construct isn't intended to be used in SELECT queries directly
- implement a direct system within CTE to detect UpdateBase and
extract columns from returning directly
|
| |
|
|
|
| |
- restore implicit returning to INSERT, UPDATE
- tests from PG's docs
|
| | |
|
| |
|
|
| |
we see that the "self.isupdate" thing is conflicting
|
| |
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
: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
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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
|
| | |
|
| |\ |
|
| | |\ |
|
| | | |
| | |
| | |
| | | |
AttributeError in object OracleCompiler_zxjdbc
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
temp tables are reflectable on the same session they were
created
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | | |
| | |
| | |
| | |
| | | |
and this time also fix the cext itself to properly handle int vs. long
on py2k
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit de0d144a395c31eb74084177df95a4858b830f88.
Apparently the test suite is not using the cextensions correctly at the moment.
|
| | | | |
|
| | |/
|/|
| |
| |
| | |
what's given so we need to use a set() here. contains_column is not within
any performance paths
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
as subqueries in order to work around SQLite's lack of support for this
syntax, is lifted when SQLite version 3.7.16 or greater is detected.
fixes #3634
- The workaround for SQLite's unexpected delivery of column names as
``tablename.columnname`` for some kinds of queries is now disabled
when SQLite version 3.10.0 or greater is detected.
fixes #3633
|
| | |
| |
| |
| |
| |
| | |
profiling problems here
- add extras_require to setup.py for the most common DBAPIs
- rework tox.ini to use extras, specify a test matrix built in
|
| | |
| |
| |
| | |
per server
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| |
| |
| |
| |
| |
| | |
available mapper options. This allows a DELETE to proceed
for a joined-table inheritance mapping against the base table only,
while allowing for ON DELETE CASCADE to handle deleting the row
from the subclass tables.
fixes #2349
|
| | |
| |
| |
| |
| | |
when attempting to compile a query that includes "offset"; Sybase
has no straightforward "offset" feature. fixes #2278
|
| | |
| |
| |
| | |
create confusion for inherited classes such as BYTEA, fixes
|
| | | |
|
| | |
| |
| |
| |
| | |
- remove redundant concrete helper docs from declarative docs,
two places is enough
|
| | |
| |
| |
| | |
when cross-compiling from DDL to SQL, fixes #3615
|
| | |
| |
| | |
Prior to this change a value of `'{}'` would split into the list `['']`.
|
| | |
| |
| |
| |
| | |
is random; therefore it may be called against the subclass mapper first, so
need to check .concrete on both sides, references #3630
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
when the construct contains non-standard sql elements such as
returning, array index operations, or dialect-specific or custom
datatypes. a string is now returned in these cases rendering an
approximation of the construct (typically the postgresql-style
version of it) rather than raising an error. fixes #3631
- add within_group to top-level imports
- add eq_ignore_whitespace to sqlalchemy.testing imports
|