| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
postgresql_tablespace option was already supported on table but not on
index.
|
| | |
|
| |
|
|
|
| |
- 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.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
temp tables are reflectable on the same session they were
created
|
| | | | |
|
| | | |
| | |
| | |
| | | |
since SQLAlchemy gets installed as develop and in the virtualenv
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | | |
| | |
| | |
| | |
| | | |
many more combinations of factors are possible and basically make them
more akin to command options at the tox level.
|
| | | |
| | |
| | |
| | |
| | | |
and this time also fix the cext itself to properly handle int vs. long
on py2k
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
in df3f125bd84fc7ec5d45592c5774daf3a39d9bc9, this flag is
explicitly checked within conftest.py and we need to continue to use
it, otherwise a tox build inside of .tox that isn't usedevelop
is ignored, including C extensions
- rework the whole system of running with coverage, so that
with coverage, we *are* using usedevelop, but also make sure
we rm the .so files for nocext, make sure we --cov-append, etc.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | |
| |
| |
| | |
interferes with coverage
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
https://github.com/pypa/virtualenv/issues/596
|
| | |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| |
| |
| |
| | |
at the primary key of a row based on other tests invoking around it
(cherry picked from commit 7d70dfd412c05fd8349339da01b472bd3df02082)
|
| | | |
|
| | |
| |
| |
| | |
references #3638
|
| | | |
|
| | |
| |
| |
| | |
per server
|
| | |
| |
| |
| | |
w/ the number of drivers /DBURIs / python versions
|
| | |
| |
| |
| | |
- test_query isn't assertscompiledsql
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|