summaryrefslogtreecommitdiff
path: root/doc/build
Commit message (Collapse)AuthorAgeFilesLines
* Update cascades.rstpr/246falkerson2016-03-091-1/+1
|
* - changelog for #3666, fixes #3666Mike Bayer2016-03-021-0/+9
|
* - Anonymous labeling is applied to a :attr:`.func` construct that isMike Bayer2016-02-261-0/+11
| | | | | | | | | 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-252-1/+80
| | | | | | | 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
* - Fixed bug in "to_list" conversion where a single bytes objectMike Bayer2016-02-211-0/+9
| | | | | | | 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-201-0/+26
| | | | | | | | | | | | | | | | | | | | | | | 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
|
* - Fixed bug which would cause an eagerly loaded many-to-one attributeMike Bayer2016-02-172-0/+104
| | | | | | | | 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
* - All string formatting of bound parameter sets and result rows forMike Bayer2016-02-172-0/+55
| | | | | | | | | 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-163-0/+24
| | | | to the new MutableList and MutableSet classes, fixes #3297
* - Fixed bug in :meth:`.Session.merge` where an object with a compositeMike Bayer2016-02-111-0/+10
| | | | | | | | 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-113-0/+75
| | | | | | | 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/+8
| | | | | | 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-092-1/+59
| | | | | | | | | | | | | :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
* - fully hyperlink the docstring for make_transientMike Bayer2016-02-081-0/+1
| | | | | | | | | - 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
* Fix typo in relationship persistance docsJosh Friend2016-02-031-1/+1
|
* - add literal_binds for delete() statements in addition to insert()/update()Mike Bayer2016-02-031-0/+10
| | | | | - move tests to CRUDTest - changelog, fixes #3643
* - changelog for #3621 fixes #3621Mike Bayer2016-02-021-0/+9
|
* - add changelog and migration notes for new Enum features,Mike Bayer2016-02-022-0/+92
| | | | | | | | | | | | 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
* - Fixed issue where inadvertent use of the Python ``__contains__``Mike Bayer2016-02-021-0/+11
| | | | | | | | | 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
* - The ``sqlalchemy.dialects.postgres`` module, long deprecated, isMike Bayer2016-01-292-1/+19
| | | | | | | 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-292-2/+2
|
* - revert the change first made in a6fe4dc, as we are now generalizingMike Bayer2016-01-281-0/+23
| | | | | | | | | | | | | | | | | | | | | | | 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
* fix %x string format to compatible with Python 3.5Ruilin Huang2016-01-271-1/+1
|
* fix %x string format to compatible with Python 3.5xghrl2016-01-271-1/+1
|
* - rework ColumnCollection to no longer persist "all_col_set"; we don'tMike Bayer2016-01-261-0/+11
| | | | | | | | | | | | | need this collection except in the extend/update uses where we create it ad-hoc. simplifies pickling. Compatibility with 1.0 should be OK as ColumnColleciton uses __getstate__ in any case and the __setstate__ contract hasn't changed. - Fixed bug in :class:`.Table` metadata construct which appeared around the 0.9 series where adding columns to a :class:`.Table` that was unpickled would fail to correctly establish the :class:`.Column` within the 'c' collection, leading to issues in areas such as ORM configuration. This could impact use cases such as ``extend_existing`` and others. fixes #3632
* - The workaround for right-nested joins on SQLite, where they are rewrittenMike Bayer2016-01-262-4/+75
| | | | | | | | | | as subqueries in order to work around SQLite's lack of support for this syntax, is lifted when SQLite version 3.7.16 or greater is detected. fixes #3634 - The workaround for SQLite's unexpected delivery of column names as ``tablename.columnname`` for some kinds of queries is now disabled when SQLite version 3.10.0 or greater is detected. fixes #3633
* - add a new qualifier "native" vs. "dbapi" unicode to avoidMike Bayer2016-01-241-2/+2
| | | | | | profiling problems here - add extras_require to setup.py for the most common DBAPIs - rework tox.ini to use extras, specify a test matrix built in
* - restate the "secondary" / AssociationProxy warning more strongly.Mike Bayer2016-01-231-10/+52
| | | | references #3638
* - documenation updates to clarify specific SQLite versionsMike Bayer2016-01-211-1/+7
| | | | | | | | | that have problems with right-nested joins and UNION column keys; references #3633 references #3634. backport from 1.1 to 0.9 announcing 1.1 as where these behaviors will be retired based on version-specific checks - fix test_resultset so that it passes when SQLite 3.10.0 is present, references #3633
* - Added new parameter :paramref:`.orm.mapper.passive_deletes` toMike Bayer2016-01-204-1/+87
| | | | | | | | available mapper options. This allows a DELETE to proceed for a joined-table inheritance mapping against the base table only, while allowing for ON DELETE CASCADE to handle deleting the row from the subclass tables. fixes #2349
* - The unsupported Sybase dialect now raises ``NotImplementedError``Mike Bayer2016-01-201-0/+8
| | | | | when attempting to compile a query that includes "offset"; Sybase has no straightforward "offset" feature. fixes #2278
* - generalize the verbiage on LargeBinary so that it doesn'tMike Bayer2016-01-201-2/+0
| | | | create confusion for inherited classes such as BYTEA, fixes
* - cross link for concrete helper classesMike Bayer2016-01-202-71/+20
| | | | | - remove redundant concrete helper docs from declarative docs, two places is enough
* - typoMike Bayer2016-01-201-1/+1
| | | | (cherry picked from commit b53667526eb9b2fabccfb097a5b76906d6452249)
* - redo the docs for concrete inheritance to more stronglyMike Bayer2016-01-202-50/+241
| | | | favor declarative, fixes #2890
* - clarify the "Adding" section also illustrates updates, fixes #2942Mike Bayer2016-01-201-3/+6
|
* - calling str() on a core sql construct has been made more "friendly",Mike Bayer2016-01-192-0/+45
| | | | | | | | | | when the construct contains non-standard sql elements such as returning, array index operations, or dialect-specific or custom datatypes. a string is now returned in these cases rendering an approximation of the construct (typically the postgresql-style version of it) rather than raising an error. fixes #3631 - add within_group to top-level imports - add eq_ignore_whitespace to sqlalchemy.testing imports
* - Fixed issue where two same-named relationships that refer toMike Bayer2016-01-192-0/+73
| | | | | | | | a base class and a concrete-inherited subclass would raise an error if those relationships were set up using "backref", while setting up the identical configuration using relationship() instead with the conflicting names would succeed, as is allowed in the case of a concrete mapping. fixes #3630
* - The ``str()`` call for :class:`.Query` will now take into accountMike Bayer2016-01-192-1/+40
| | | | | | | | | | | | the :class:`.Engine` to which the :class:`.Session` is bound, when generating the string form of the SQL, so that the actual SQL that would be emitted to the database is shown, if possible. Previously, only the engine associated with the :class:`.MetaData` to which the mappings are associated would be used, if present. If no bind can be located either on the :class:`.Session` or on the :class:`.MetaData` to which the mappings are associated, then the "default" dialect is used to render the SQL, as was the case previously. fixes #3081
* - Fixed bug where some exception re-raise scenarios would attachMike Bayer2016-01-181-0/+8
| | | | | | | | the exception to itself as the "cause"; while the Python 3 interpreter is OK with this, it could cause endless loops in iPython. fixes #3625 - add tests for reraise, raise_from_cause - raise_from_cause is the same on py2k/3k, use just one function
* Merge remote-tracking branch 'origin/pr/227'Mike Bayer2016-01-161-2/+2
|\
| * Fix typo in relationships docspr/227rmn2016-01-161-2/+2
| |
* | - fix People -> Person , fixes #3628Mike Bayer2016-01-161-1/+1
|/
* - updateMike Bayer2016-01-141-1/+1
|
* - illustrate these using the newer exception doctest format.Mike Bayer2016-01-141-26/+8
| | | | | unfortunately we can't show the SQL unless we filtered it out from doctest...not worth it
* - A deep improvement to the recently added :meth:`.TextClause.columns`Mike Bayer2016-01-145-58/+333
| | | | | | | | | | | | | | | | | | | method, and its interaction with result-row processing, now allows the columns passed to the method to be positionally matched with the result columns in the statement, rather than matching on name alone. The advantage to this includes that when linking a textual SQL statement to an ORM or Core table model, no system of labeling or de-duping of common column names needs to occur, which also means there's no need to worry about how label names match to ORM columns and so-forth. In addition, the :class:`.ResultProxy` has been further enhanced to map column and string keys to a row with greater precision in some cases. fixes #3501 - reorganize the initialization of ResultMetaData for readability and complexity; use the name "cursor_description", define the task of "merging" cursor_description with compiled column information as its own function, and also define "name extraction" as a separate task. - fully change the name we use in the "ambiguous column" error to be the actual name that was ambiguous, modify the C ext also
* - changelog for pr bitbucket:70, fixes #3624Mike Bayer2016-01-121-0/+9
|
* - fix link to types in metadata, fixes #3618Mike Bayer2016-01-103-3/+3
| | | | | | - fix "version" got whacked into "f" in core tutorial - fix short underline in automap - fix unmatched boldface in session events
* Merge remote-tracking branch 'origin/pr/225'Mike Bayer2016-01-101-1/+1
|\
View Lorry Controller Status