summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Add `sqlalchemy.ext.mutable.MutableSet`pr/236Jeong YunWon2016-02-132-1/+260
| | | | from https://bitbucket.org/zzzeek/sqlalchemy/issues/3297
* Add `sqlalchemy.ext.mutable.MutableList`Jeong YunWon2016-02-132-1/+297
|
* - Fixed bug in :meth:`.Session.merge` where an object with a compositeMike Bayer2016-02-113-3/+63
| | | | | | | | 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
* - CTE functionality has been expanded to support all DML, allowingMike Bayer2016-02-1112-177/+503
| | | | | | | 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
* - add more documentation to MutableDict explainingMike Bayer2016-02-101-0/+12
| | | | | | that this structure is only intended to track additions and removals from the dictionary, not recursive tracking of embedded changes. fixes #3646.
* - don't drop the ts1/ts2 databases without seeing the primary DB,Mike Bayer2016-02-091-6/+21
| | | | | because we never log in on the ts1/ts2. races against other runs and erases their DBs
* - Fixed bug in :func:`.expression.text` construct where a double-colonMike Bayer2016-02-092-0/+19
| | | | | | expression would not escape properly, e.g. ``some\:\:expr``, as is most commonly required when rendering Postgresql-style CAST expressions. fixes #3644
* - A refinement to the logic which adds columns to the resulting SQL whenMike Bayer2016-02-095-23/+229
| | | | | | | | | | | | | :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
* - switch to 2 workers for oracleMike Bayer2016-02-091-2/+4
|
* - Testing reveals that we have *no* weak references to any cx_Oracle ↵Mike Bayer2016-02-083-9/+58
| | | | | | | | 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.
* - use config-based test schemaMike Bayer2016-02-081-5/+5
|
* - attempt a different style of session killMike Bayer2016-02-081-1/+2
|
* - fully hyperlink the docstring for make_transientMike Bayer2016-02-083-12/+49
| | | | | | | | | - 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
* - additional fixes to get oracle + multiprocess to be reliableMike Bayer2016-02-083-1/+12
|
* - py3k fix for enum featureMike Bayer2016-02-081-1/+4
|
* - add missing __backend__ directives for SQL serverMike Bayer2016-02-082-0/+6
|
* - add missing __backend__ directives so that oracle tests actually run with ↵Mike Bayer2016-02-081-0/+17
| | | | --backend-only
* - detect "Enterprise" and assume compression stuff isn't availableMike Bayer2016-02-081-0/+6
| | | | if not
* - adjust the MultiSchemaTest to handle multiple test_schemas / processes at theMike Bayer2016-02-081-5/+6
| | | | same time
* - adjust to allow dblink tests to work with multiprocess users.Mike Bayer2016-02-082-10/+4
| | | | | | 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.
* - add a session killer for oracle provisioningMike Bayer2016-02-041-0/+5
|
* - add an impl for Enum to Oracle which has subclassing requirementsMike Bayer2016-02-041-0/+13
| | | | | | | 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...)
* - more oracle fixesMike Bayer2016-02-032-5/+10
|
* - oracle requires GLOBAL hereMike Bayer2016-02-032-2/+2
|
* - add multi-database provisioning for oracleMike Bayer2016-02-031-0/+29
|
* Fix typo in relationship persistance docsJosh Friend2016-02-031-1/+1
|
* - add literal_binds for delete() statements in addition to insert()/update()Mike Bayer2016-02-033-17/+36
| | | | | - move tests to CRUDTest - changelog, fixes #3643
* fix passing literal_binds flag through for update and insertpr/232Tim Tate2016-02-023-4/+21
|
* - changelog for #3621 fixes #3621Mike Bayer2016-02-021-0/+9
|
* Merge branch 'master' of https://bitbucket.org/carlrivers/sqlalchemyMike Bayer2016-02-021-2/+1
|\
| * Merged zzzeek/sqlalchemy into masterCarlos Rivas2016-01-26115-3287/+6926
| |\
| * \ Merged in carlrivers/removed-entry-that-causes-attributeerror-1453541002643 ↵Carlos Rivas2016-01-231-2/+1
| |\ \ | | | | | | | | | | | | | | | | | | | | (pull request #1) Removed entry that causes AttributeError (#3621) - Oracle zxJDBC fails with AttributeError in object OracleCompiler_zxjdbc
| | * | Removed entry that causes AttributeError (#3621) - Oracle zxJDBC fails with ↵Carlos Rivas2016-01-231-2/+1
| |/ / | | | | | | | | | AttributeError in object OracleCompiler_zxjdbc
* | | - test fixes for metadata.enums value now being a listMike Bayer2016-02-022-24/+20
| | | | | | | | | | | | - modernize those tests as well
* | | - add changelog and migration notes for new Enum features,Mike Bayer2016-02-026-110/+393
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | - Initial implementation of support for PEP-435 enumerated typesAlex Grönholm2016-02-022-34/+128
| | | | | | | | | | | | within the Enum type.
* | | - D rules seem to have been added overnight to the flake8 pluginMike Bayer2016-02-021-1/+1
| | | | | | | | | | | | | | | I'm using and many of these seem contradictory and/or undesirable. block all until individual rules can be approved.
* | | - Fixed issue where inadvertent use of the Python ``__contains__``Mike Bayer2016-02-025-2/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | - put a retry in for PG database provisioning as it locksMike Bayer2016-01-291-1/+14
| | | | | | | | | | | | on database use
* | | - The ``sqlalchemy.dialects.postgres`` module, long deprecated, isMike Bayer2016-01-295-19/+38
| | | | | | | | | | | | | | | | | | | | | 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.
* | | - happy new yearMike Bayer2016-01-29177-177/+177
| | |
* | | - use a StaticPool for componentreflectiontest to ensureMike Bayer2016-01-281-7/+16
| | | | | | | | | | | | | | | temp tables are reflectable on the same session they were created
* | | - use schema argument correctly when we are dropping for a schemaMike Bayer2016-01-281-1/+1
| | |
* | | - using extras here has the effect of defeating the usedevelop flagMike Bayer2016-01-281-6/+6
| | | | | | | | | | | | since SQLAlchemy gets installed as develop and in the virtualenv
* | | - revert the change first made in a6fe4dc, as we are now generalizingMike Bayer2016-01-287-18/+93
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | - experimental - try out a very open ended design for the factors, assumeMike Bayer2016-01-271-26/+15
| | | | | | | | | | | | | | | many more combinations of factors are possible and basically make them more akin to command options at the tox level.
* | | - reinstate "dont set up integer index in keymap if we're on cexts",Mike Bayer2016-01-272-6/+11
| | | | | | | | | | | | | | | and this time also fix the cext itself to properly handle int vs. long on py2k
* | | - restore the use of PYTHONNOUSERSITE that was removedMike Bayer2016-01-272-6/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | Revert "- dont set up integer index in keymap if we're on cexts"Mike Bayer2016-01-271-10/+5
| | | | | | | | | | | | | | | | | | This reverts commit de0d144a395c31eb74084177df95a4858b830f88. Apparently the test suite is not using the cextensions correctly at the moment.
* | | - dont set up integer index in keymap if we're on cextsMike Bayer2016-01-271-5/+10
| | |
View Lorry Controller Status