summaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAgeFilesLines
...
* Merge "Deprecate Mapper.order_by"mike bayer2016-04-1915-61/+111
|\
| * Deprecate Mapper.order_byMike Bayer2016-04-1915-61/+111
| | | | | | | | | | | | | | | | | | | | | | This is an old parameter no longer relevant to how SQLAlchemy works, once the Query object was introduced. By deprecating it we establish that we aren't supporting non-working use cases and that we encourage applications to move off of the use of this parameter. Fixes: #3394 Change-Id: I25b9a38142a1537bbcb27d3e8b66a8b265140072
* | Rename Query._mapper_zero() to Query._entity_zero()Mike Bayer2016-04-192-6/+7
|/ | | | | | | | | | | | To be more descriptive of the use of _mapper_zero(), rename it to _entity_zero(), but also supply a new _mapper_zero() function that more strictly returns a mapper. The existing _entity_zero() function is renamed to _query_entity_zero. _only_mapper_zero() is removed as it isn't used. Divide up the existing calling functions to refer to the appropriate new method. Change-Id: I8780c3235e87b4936c6daf64d9d299b22b6e1260 Fixes: #3608
* Merge "Add raise/raiseload relationship loading strategy"mike bayer2016-04-191-0/+109
|\
| * Add raise/raiseload relationship loading strategyAdrian Moennich2016-04-191-0/+109
| | | | | | | | | | | | | | Fixes: #3512 Co-Authored-By: Mike Bayer <mike_mp@zzzcomputing.com> Change-Id: Ibd126c50eda621e2f4120ee378f7313af2d7ec3c Pull-request: https://github.com/zzzeek/sqlalchemy/pull/193
* | Propagate hybrid properties / infoMike Bayer2016-04-181-0/+53
| | | | | | | | | | | | | | | | | | | | | | Keystone and others depend on the .property attribute being "mirrored" when a @hybrid_property is linked directly to a mapped attribute. Restore this linkage and also create a defined behavior for the .info dictionary; it is that of the hybrid itself. Add this behavioral change to the migration notes. Change-Id: I8ac34ef52039387230c648866c5ca15d381f7fee References: #3653
* | Honor hybrid property / method docstringsMike Bayer2016-04-182-11/+288
| | | | | | | | | | | | | | | | | | | | | | | | The docstring specified on a hybrid property or method is now honored at the class level, allowing it to work with tools like Sphinx autodoc. The mechanics here necessarily involve some wrapping of expressions to occur for hybrid properties, which may cause them to appear differently using introspection. Fixes: #3653 Change-Id: I02549977fe8b2a051802eed7b00cc532fbc214e3 Pull-request: https://github.com/zzzeek/sqlalchemy/pull/239
* | - Add support for PostgreSQL with PyGreSQLChristoph Zwerschke2016-04-153-7/+11
|/ | | | | Change-Id: I040b75ff3b4110e7e8b26442a4eb226ba8c26715 Pull-request: https://github.com/zzzeek/sqlalchemy/pull/234
* - don't load deferred columns on unexpire for merge with load=False,Diana Clarke2016-04-061-4/+100
| | | | | | | fixes #3488 Change-Id: Ic9577b800e4a4e2465ec7f3a2e95bd231f5337ee Co-Authored-By: Mike Bayer <mike_mp@zzzcomputing.com>
* - callcount refresh due to negative indexes change for nocextMike Bayer2016-03-311-247/+299
|
* - limit this to sqlite for nowMike Bayer2016-03-301-0/+1
|
* - move all resultproxy tests intio test_resultsetMike Bayer2016-03-302-333/+336
|
* - make sure negative row indexes are based on the size of theMike Bayer2016-03-301-14/+22
| | | | | | number of columns we're actually reporting on - add more tests for negative row index - changelog/migration
* Merge remote-tracking branch 'origin/pr/231' into pr231Mike Bayer2016-03-301-0/+19
|\
| * - properly handle negative indexes in RowProxy.__getitem__()pr/231Lele Gaifax2016-01-281-0/+19
| |
* | Merge remote-tracking branch 'origin/pr/230'Mike Bayer2016-03-302-4/+35
|\ \
| * | sqlite: reflect primary key constraint names, fixes #3629Diana Clarke2016-01-272-4/+35
| | |
* | | - 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
View Lorry Controller Status