summaryrefslogtreecommitdiff
path: root/lib
Commit message (Collapse)AuthorAgeFilesLines
* 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
* - A refinement to the logic which adds columns to the resulting SQL whenMike Bayer2016-02-092-15/+33
| | | | | | | | | | | | | :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
* - Testing reveals that we have *no* weak references to any cx_Oracle ↵Mike Bayer2016-02-081-9/+32
| | | | | | | | 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
|
* - fully hyperlink the docstring for make_transientMike Bayer2016-02-082-12/+48
| | | | | | | | | - establish make_transient and make_transient_to_detached as special-use, advanced use only functions - list all conditions under make_transient() under which an attribute will not be loaded and establish that make_transient() does not attempt to load all attributes before detaching the object from its session, fixes #3640
* - additional fixes to get oracle + multiprocess to be reliableMike Bayer2016-02-082-0/+11
|
* - py3k fix for enum featureMike Bayer2016-02-081-1/+4
|
* - add a session killer for oracle provisioningMike Bayer2016-02-041-0/+5
|
* - add an impl for Enum to Oracle which has subclassing requirementsMike Bayer2016-02-041-0/+13
| | | | | | | on unicode. Enum would be better as a TypeDecorator at this point but then that becomes awkward with native enum types (Interval works that way, but we don't need the bind_processor for native interval...)
* - more oracle fixesMike Bayer2016-02-032-5/+10
|
* - oracle requires GLOBAL hereMike Bayer2016-02-032-2/+2
|
* - add multi-database provisioning for oracleMike Bayer2016-02-031-0/+29
|
* - add literal_binds for delete() statements in addition to insert()/update()Mike Bayer2016-02-031-1/+1
| | | | | - move tests to CRUDTest - changelog, fixes #3643
* fix passing literal_binds flag through for update and insertpr/232Tim Tate2016-02-022-4/+5
|
* Merge branch 'master' of https://bitbucket.org/carlrivers/sqlalchemyMike Bayer2016-02-021-2/+1
|\
| * Merged zzzeek/sqlalchemy into masterCarlos Rivas2016-01-2658-2090/+3371
| |\
| * | Removed entry that causes AttributeError (#3621) - Oracle zxJDBC fails with ↵Carlos Rivas2016-01-231-2/+1
| | | | | | | | | | | | AttributeError in object OracleCompiler_zxjdbc
* | | - add changelog and migration notes for new Enum features,Mike Bayer2016-02-022-74/+143
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-5/+72
| | | | | | | | | | | | within the Enum type.
* | | - Fixed issue where inadvertent use of the Python ``__contains__``Mike Bayer2016-02-022-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | - put a retry in for PG database provisioning as it locksMike Bayer2016-01-291-1/+14
| | | | | | | | | | | | on database use
* | | - The ``sqlalchemy.dialects.postgres`` module, long deprecated, isMike Bayer2016-01-292-18/+9
| | | | | | | | | | | | | | | | | | | | | 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.
* | | - happy new yearMike Bayer2016-01-29174-174/+174
| | |
* | | - use a StaticPool for componentreflectiontest to ensureMike Bayer2016-01-281-7/+16
| | | | | | | | | | | | | | | temp tables are reflectable on the same session they were created
* | | - use schema argument correctly when we are dropping for a schemaMike Bayer2016-01-281-1/+1
| | |
* | | - revert the change first made in a6fe4dc, as we are now generalizingMike Bayer2016-01-282-14/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | - reinstate "dont set up integer index in keymap if we're on cexts",Mike Bayer2016-01-272-6/+11
| | | | | | | | | | | | | | | and this time also fix the cext itself to properly handle int vs. long on py2k
View Lorry Controller Status