summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy
Commit message (Collapse)AuthorAgeFilesLines
* Fix pymssql sample URLMike Bayer2016-04-271-1/+1
| | | | | | | | A slash is required before building out the query string portion. Change-Id: Ie97fd3d07047d78e17cbaffed4ff54960a2b956e Fixes: #3696 (cherry picked from commit 83a9e6e1fac276090e60136aa4e9234ae23bc25a)
* Merge remote-tracking branch 'origin/pr/263'Mike Bayer2016-04-271-7/+7
|\
| * Adds parentheses around prints in documentationpr/263jfinkels2016-04-271-7/+7
| | | | | | This makes the docstring example code compatible with both Python 2 and Python 3.
* | Don't double-process ResultMetaData for BufferedColumnResultProxyMike Bayer2016-04-271-9/+15
|/ | | | | | | | | | | | Fixed a bug in the result proxy used mainly by Oracle when binary and other LOB types are in play, such that when query / statement caching were used, the type-level result processors, notably that required by the binary type itself but also any other processor, would become lost after the first run of the statement due to it being removed from the cached result metadata. Change-Id: I751940866cffb4f48de46edc8137482eab59790c Fixes: #3699
* Fix result set handling for case insensitive dupe colsMike Bayer2016-04-211-0/+1
| | | | | | | | | | | Fixed bug where when using ``case_sensitive=False`` with an :class:`.Engine`, the result set would fail to correctly accomodate for duplicate column names in the result set, causing an error when the statement is executed in 1.0, and preventing the "ambiguous column" exception from functioning in 1.1. Change-Id: If582bb9fdd057e4da3ae42f7180b17d1a1a2d98e Fixes: #3690
* Merge "Deprecate Mapper.order_by"mike bayer2016-04-191-0/+9
|\
| * Deprecate Mapper.order_byMike Bayer2016-04-191-0/+9
| | | | | | | | | | | | | | | | | | | | | | 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-191-17/+15
|/ | | | | | | | | | | | 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-194-0/+65
|\
| * Add raise/raiseload relationship loading strategyAdrian Moennich2016-04-194-0/+65
| | | | | | | | | | | | | | 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-1/+12
| | | | | | | | | | | | | | | | | | | | | | 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-181-5/+25
| | | | | | | | | | | | | | | | | | | | | | | | 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-2/+248
|/ | | | | Change-Id: I040b75ff3b4110e7e8b26442a4eb226ba8c26715 Pull-request: https://github.com/zzzeek/sqlalchemy/pull/234
* 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
View Lorry Controller Status