summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy
Commit message (Collapse)AuthorAgeFilesLines
* Spelling fixespr/266Ville Skyttä2016-05-0339-101/+101
|
* Merge remote-tracking branch 'origin/pr/257'Mike Bayer2016-04-081-1/+2
|\
| * Mention the correct way of adding multiple attributes which refer to the ↵pr/257Eoghan Murray2016-04-071-1/+2
| | | | | | | | same column
* | Fix typo from "addreses" to "addresses"Rachid Belaid2016-04-061-1/+1
|/
* Merge "- don't load deferred columns on unexpire for merge with load=False, ↵mike bayer2016-04-063-2/+20
|\ | | | | | | fixes #3488"
| * - don't load deferred columns on unexpire for merge with load=False,Diana Clarke2016-04-063-2/+20
| | | | | | | | | | | | | | fixes #3488 Change-Id: Ic9577b800e4a4e2465ec7f3a2e95bd231f5337ee Co-Authored-By: Mike Bayer <mike_mp@zzzcomputing.com>
* | Fix some broken links in docspr/255Ville Skyttä2016-04-041-1/+1
|/
* - make sure negative row indexes are based on the size of theMike Bayer2016-03-301-1/+4
| | | | | | 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-302-1/+12
|\
| * - properly handle negative indexes in RowProxy.__getitem__()pr/231Lele Gaifax2016-01-282-1/+12
| |
* | Merge remote-tracking branch 'origin/pr/230'Mike Bayer2016-03-301-1/+9
|\ \
| * | same logic, but without the inner functionpr/230Diana Clarke2016-01-281-4/+3
| | |
| * | sqlite: reflect primary key constraint names, fixes #3629Diana Clarke2016-01-271-1/+10
| | |
* | | - Added :meth:`.Select.lateral` and related constructs to allowMike Bayer2016-03-296-10/+79
| | | | | | | | | | | | | | | 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-285-35/+78
| | | | | | | | | | | | Pull request courtesy Stefan Urbanek. fixes #1957
* | | - remember to not reassign self.connection now that __connect()Mike Bayer2016-03-251-2/+2
| | | | | | | | | | | | has no return value
* | | - Added connection pool events :meth:`ConnectionEvents.close`,Mike Bayer2016-03-252-22/+70
| | | | | | | | | | | | | | | :meth:`.ConnectionEvents.detach`, :meth:`.ConnectionEvents.close_detached`.
* | | - Further continuing on the common MySQL exception case ofMike Bayer2016-03-231-12/+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
* | | Merge remote-tracking branch 'origin/pr/251'Mike Bayer2016-03-211-1/+1
|\ \ \
| * | | ReST fix: missing backtickpr/251Marius Gedminas2016-03-211-1/+1
| | | | | | | | | | | | Fixes a misrendering at http://docs.sqlalchemy.org/en/latest/dialects/mssql.html#nullability:
* | | | - Fixed bug where the negation of an EXISTS expression would notMike Bayer2016-03-212-1/+13
|/ / / | | | | | | | | | | | | | | | | | | 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
* | | - 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-152-0/+88
| | | | | | | | | | | | | | | | | | 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-152-13/+39
| | | | | | | | | | | | | | | | | | - make docs for isolation level more consistent between postgresql and mysql - move mysql autocommit tests
* | | Merge branch 'master' into pr157Mike Bayer2016-03-15186-5016/+12327
|\ \ \
| * | | - 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-142-16/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| | | |
| * | | - not sure why MySQL DROP DBs fail but we can't just ignore the errorMike Bayer2016-03-031-12/+3
| | | | | | | | | | | | | | | | like this
| * | | 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-261-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-5/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-212-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * | | - reworked the way the "select_wraps_for" expression isMike Bayer2016-02-204-13/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | | - 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-171-7/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-173-2/+6
| | | | | | | | | | | | | | | | | | | | 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-4/+7
| | | |
| * | | - All string formatting of bound parameter sets and result rows forMike Bayer2016-02-172-13/+110
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-161-1/+41
| | | | | | | | | | | | | | | | to the new MutableList and MutableSet classes, fixes #3297
| * | | Merge remote-tracking branch 'origin/pr/236'Mike Bayer2016-02-161-0/+144
| |\ \ \
| | * | | Add `sqlalchemy.ext.mutable.MutableSet`pr/236Jeong YunWon2016-02-131-0/+65
| | | | | | | | | | | | | | | | | | | | from https://bitbucket.org/zzzeek/sqlalchemy/issues/3297
| | * | | Add `sqlalchemy.ext.mutable.MutableList`Jeong YunWon2016-02-131-0/+79
| | | | |
| * | | | - 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-111-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-117-173/+275
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
View Lorry Controller Status