summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* adapt test for raising on empty includepr/250Sebastian Bank2016-03-211-1/+1
|
* adapt error message wording, raise on empty includeSebastian Bank2016-03-201-4/+7
|
* simplify include arg processingSebastian Bank2016-03-191-8/+2
|
* adapt inspector for new include arg of postgres get_view_names, add testsSebastian Bank2016-03-192-3/+15
|
* refactor get_schema_names (apply filter in the query)Sebastian Bank2016-03-171-15/+6
|
* refactor table_names methods dropping sql string interpolation and subselectSebastian Bank2016-03-171-28/+12
|
* extend get_view_names to select wanted view kind (plain and/or materialized)Sebastian Bank2016-03-171-52/+31
| | | | also: simplify get_view_definition
* Fix typopr/249Benjamin Dopplinger2016-03-161-1/+1
|
* - ensure engine is restored even if we had a failure in cleanupMike Bayer2016-03-151-3/+5
| | | | for stray connection
* - Added basic isolation level support to the SQL Server dialectsMike Bayer2016-03-156-1/+128
| | | | | | 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-155-36/+94
| | | | | | - make docs for isolation level more consistent between postgresql and mysql - move mysql autocommit tests
* Merge branch 'master' into pr157Mike Bayer2016-03-15363-10581/+39843
|\
| * - add notes for pyodbc limitations with rowcount fixes #3675Mike Bayer2016-03-152-0/+41
| |
| * - Fixed bug where a newly inserted instance that is rolled backMike Bayer2016-03-145-17/+163
| | | | | | | | | | | | | | | | | | 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
| * Adds documentation to Query.slice().pr/247jfinkels2016-03-131-3/+28
| |
| * Update cascades.rstpr/246falkerson2016-03-091-1/+1
| |
| * - skip GC tests here when coverage is enabled, seems to interfereMike Bayer2016-03-081-1/+1
| |
| * - not sure why MySQL DROP DBs fail but we can't just ignore the errorMike Bayer2016-03-031-12/+3
| | | | | | | | like this
| * - 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
| * - changelog for #3666, fixes #3666Mike Bayer2016-03-021-0/+9
| |
| * Add test for inserting multiple valuesAthena Yao2016-03-021-0/+38
| |
| * Raise exception when we have multiple values with an unknown column. Fixes ↵Athena Yao2016-03-021-1/+1
| | | | | | | | #3666.
| * - unfortunately calling upon "_label" here makes it unclear ifMike Bayer2016-02-261-2/+4
| | | | | | | | | | | | | | we're trying to hit columns without names yet and such, to suit the bug right now just make it specific to FunctionElement (cherry picked from commit 785224a92f39bd5bdd05bbc66f4dd79736abded5)
| * - Anonymous labeling is applied to a :attr:`.func` construct that isMike Bayer2016-02-263-2/+70
| | | | | | | | | | | | | | | | | | 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-254-9/+160
| | | | | | | | | | | | | | 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-212-1/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-214-3/+30
| | | | | | | | | | | | | | 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-209-16/+110
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * Add release date for 1.0.12 to changelogpr/241Jeff Widman2016-02-191-1/+1
| |
| * - further edit the unnest() example to suit PG's esoteric requirementsMike Bayer2016-02-181-4/+6
| | | | | | | | exactly
| * - Fixed bug which would cause an eagerly loaded many-to-one attributeMike Bayer2016-02-174-9/+264
| | | | | | | | | | | | | | | | 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-174-3/+33
| | | | | | | | | | 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-172-4/+25
| |
| * - All string formatting of bound parameter sets and result rows forMike Bayer2016-02-175-14/+250
| | | | | | | | | | | | | | | | | | 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 changelog, migration, version flags and some extra notesMike Bayer2016-02-164-1/+65
| | | | | | | | to the new MutableList and MutableSet classes, fixes #3297
| * Merge remote-tracking branch 'origin/pr/236'Mike Bayer2016-02-162-1/+556
| |\
| | * 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
| | |
| * | - use same colname as the alias we give to the PG functionMike Bayer2016-02-161-2/+2
| |/ | | | | | | here, fixes #3652
| * - 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
| |
View Lorry Controller Status