summaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAgeFilesLines
* - Added :meth:`.Select.lateral` and related constructs to allowMike Bayer2016-03-291-0/+134
| | | | | for the SQL standard LATERAL keyword, currently only supported by Postgresql. fixes #2857
* - Added support for rendering "FULL OUTER JOIN" to both Core and ORM.Mike Bayer2016-03-283-0/+56
| | | | Pull request courtesy Stefan Urbanek. fixes #1957
* - Added connection pool events :meth:`ConnectionEvents.close`,Mike Bayer2016-03-251-0/+60
| | | | | :meth:`.ConnectionEvents.detach`, :meth:`.ConnectionEvents.close_detached`.
* - oracle doesn't release savepointsMike Bayer2016-03-241-1/+1
|
* - Further continuing on the common MySQL exception case ofMike Bayer2016-03-231-2/+31
| | | | | | | | | a savepoint being cancelled first covered in :ticket:`2696`, the failure mode in which the :class:`.Session` is placed when a SAVEPOINT vanishes before rollback has been improved to allow the :class:`.Session` to still function outside of that savepoint. It is assumed that the savepoint operation failed and was cancelled. fixes #3680
* - Fixed bug where the negation of an EXISTS expression would notMike Bayer2016-03-212-0/+42
| | | | | | | be properly typed as boolean in the result, and also would fail to be anonymously aliased in a SELECT list as is the case with a non-negated EXISTS construct. fixes #3682
* - Added basic isolation level support to the SQL Server dialectsMike Bayer2016-03-152-1/+5
| | | | | | via :paramref:`.create_engine.isolation_level` and :paramref:`.Connection.execution_options.isolation_level` parameters. fixes #3534
* - changelog and docs for #3332, fixes #3332Mike Bayer2016-03-151-23/+24
| | | | | | - make docs for isolation level more consistent between postgresql and mysql - move mysql autocommit tests
* Merge branch 'master' into pr157Mike Bayer2016-03-15104-4399/+18566
|\
| * - Fixed bug where a newly inserted instance that is rolled backMike Bayer2016-03-141-1/+25
| | | | | | | | | | | | | | | | | | would still potentially cause persistence conflicts on the next transaction, because the instance would not be checked that it was expired. This fix will resolve a large class of cases that erronously cause the "New instance with identity X conflicts with persistent instance Y" error. fixes #3677
| * - skip GC tests here when coverage is enabled, seems to interfereMike Bayer2016-03-081-1/+1
| |
| * - move out unconsumed names tests from test_compiler out to test_insert, ↵Mike Bayer2016-03-023-48/+62
| | | | | | | | | | | | | | test_update - establish consistent names between existing unconsumed names tests and new ones added per ref #3666
| * Add test for inserting multiple valuesAthena Yao2016-03-021-0/+38
| |
| * - Anonymous labeling is applied to a :attr:`.func` construct that isMike Bayer2016-02-261-1/+58
| | | | | | | | | | | | | | | | | | passed to :func:`.column_property`, so that if the same attribute is referred to as a column expression twice the names are de-duped, thus avoiding "ambiguous column" errors. Previously, the ``.label(None)`` would need to be applied in order for the name to be de-anonymized. fixes #3663
| * - An improvement to the workings of :meth:`.Query.correlate` suchMike Bayer2016-02-251-3/+72
| | | | | | | | | | | | | | that when a "polymorphic" entity is used which represents a straight join of several tables, the statement will ensure that all the tables within the join are part of what's correlating. fixes #3662
| * - additional adjustment to the fix made in ↵Mike Bayer2016-02-211-0/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8ad968f33100baeb3b13c7e0b724b6b79ab4277f for ref #3657. The Oracle dialect makes more use of the "select_wraps_for" feature than SQL server because Oracle doesn't have "TOP" for a limit-only select, so tests are showing more happening here. In the case where the select() has some dupe columns, these are deduped from the .c collection so a positional match between the wrapper and original can't use .inner_columns, because these collections wont match. Using _columns_plus_names instead which is the deduped collection that determines the SELECT display, which definitely have to match up. (cherry picked from commit aa9ce3f521f254da9879ede011e520ec35b8270e)
| * - Fixed bug in "to_list" conversion where a single bytes objectMike Bayer2016-02-211-1/+15
| | | | | | | | | | | | | | would be turned into a list of individual characters. This would impact among other things using the :meth:`.Query.get` method on a primary key that's a bytes object. fixes #3660
| * - update the mssql autoincrement reflection test to accommodateMike Bayer2016-02-201-27/+23
| | | | | | | | the new behavior of the autoincrement flag as per ref #3216
| * - reworked the way the "select_wraps_for" expression isMike Bayer2016-02-204-3/+75
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | handled within visit_select(); this attribute was added in the 1.0 series to accommodate the subquery wrapping behavior of SQL Server and Oracle while also working with positional column targeting and no longer relying upon "key fallback" in order to target columns in such a statement. The IBM DB2 third-party dialect also has this use case, but its implementation is using regular expressions to rewrite the textual SELECT only and does not make use of a "wrapped" select at this time. The logic no longer attempts to reconcile proxy set collections as this was not deterministic, and instead assumes that the select() and the wrapper select() match their columns postionally, at least for the column positions they have in common, so it is now very simple and safe. fixes #3657. - as a side effect of #3657 it was also revealed that the strategy of calling upon a ResultProxy._getter was not correctly calling into NoSuchColumnError when an expected column was not present, and instead returned None up to loading.instances() to produce NoneType failures; added a raiseerr argument to _getter() which is called when we aren't expecting None, fixes #3658.
| * - Fixed bug which would cause an eagerly loaded many-to-one attributeMike Bayer2016-02-171-2/+147
| | | | | | | | | | | | | | | | 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
| * - handle parameter sets that aren't correctly formed, so thatMike Bayer2016-02-171-1/+27
| | | | | | | | | | for example an exception object made within a test suite can still repr (error seen in Keystone)
| * - do the trailing comma logic of tuple repr() exactlyMike Bayer2016-02-171-0/+18
| |
| * - All string formatting of bound parameter sets and result rows forMike Bayer2016-02-171-1/+85
| | | | | | | | | | | | | | | | | | 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
| * Add `sqlalchemy.ext.mutable.MutableSet`pr/236Jeong YunWon2016-02-131-1/+195
| | | | | | | | from https://bitbucket.org/zzzeek/sqlalchemy/issues/3297
| * Add `sqlalchemy.ext.mutable.MutableList`Jeong YunWon2016-02-131-1/+218
| |
| * - Fixed bug in :meth:`.Session.merge` where an object with a compositeMike Bayer2016-02-111-1/+50
| | | | | | | | | | | | | | | | 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-112-4/+153
| | | | | | | | | | | | | | 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
| * - Fixed bug in :func:`.expression.text` construct where a double-colonMike Bayer2016-02-091-0/+11
| | | | | | | | | | | | 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-091-7/+137
| | | | | | | | | | | | | | | | | | | | | | | | | | :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
| * - 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-081-9/+3
| | | | | | | | | | | | 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 literal_binds for delete() statements in addition to insert()/update()Mike Bayer2016-02-031-16/+25
| | | | | | | | | | - move tests to CRUDTest - changelog, fixes #3643
| * fix passing literal_binds flag through for update and insertpr/232Tim Tate2016-02-021-0/+16
| |
| * - 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-022-36/+158
| | | | | | | | | | | | | | | | | | | | | | | | 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-021-29/+56
| | | | | | | | within the Enum type.
| * - Fixed issue where inadvertent use of the Python ``__contains__``Mike Bayer2016-02-022-1/+32
| | | | | | | | | | | | | | | | | | 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
| * - The ``sqlalchemy.dialects.postgres`` module, long deprecated, isMike Bayer2016-01-291-0/+10
| | | | | | | | | | | | | | 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.
| * - revert the change first made in a6fe4dc, as we are now generalizingMike Bayer2016-01-284-4/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * - restore the use of PYTHONNOUSERSITE that was removedMike Bayer2016-01-271-0/+6
| | | | | | | | | | | | | | | | | | | | 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.
| * - rework ColumnCollection to no longer persist "all_col_set"; we don'tMike Bayer2016-01-261-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * - The workaround for right-nested joins on SQLite, where they are rewrittenMike Bayer2016-01-262-93/+146
| | | | | | | | | | | | | | | | | | | | 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
| * - add a new qualifier "native" vs. "dbapi" unicode to avoidMike Bayer2016-01-241-468/+404
| | | | | | | | | | | | 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
| * - fix array test that was essentially taking a weird guessMike Bayer2016-01-231-2/+2
| | | | | | | | | | | | at the primary key of a row based on other tests invoking around it (cherry picked from commit 7d70dfd412c05fd8349339da01b472bd3df02082)
| * - fix stray connectionMike Bayer2016-01-231-1/+4
| |
| * - use regex here, columns dont matter, keep coming up with different orderingsMike Bayer2016-01-231-3/+3
| |
| * - native unicode expectations are too difficult to maintainMike Bayer2016-01-231-60/+0
| | | | | | | | w/ the number of drivers /DBURIs / python versions
View Lorry Controller Status