From 75f3edf5b5384c2be26b0a17f0b8468f3fb9b3bf Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Thu, 14 Nov 2013 22:06:20 -0500 Subject: [PATCH] sync up 0.8's changelogs with 0.7.... --- doc/build/changelog/changelog_02.rst | 2 +- doc/build/changelog/changelog_03.rst | 2 +- doc/build/changelog/changelog_04.rst | 6 ++-- doc/build/changelog/changelog_06.rst | 4 +-- doc/build/changelog/changelog_07.rst | 43 ++++++++-------------------- 5 files changed, 19 insertions(+), 38 deletions(-) diff --git a/doc/build/changelog/changelog_02.rst b/doc/build/changelog/changelog_02.rst index e995b6a7c6..a2b0ab10bd 100644 --- a/doc/build/changelog/changelog_02.rst +++ b/doc/build/changelog/changelog_02.rst @@ -678,7 +678,7 @@ modified version (works in py2.3/2.4!) that uses a threading.RLock for a mutex. this is to fix a reported case where a ConnectionFairy's __del__() method got called within the Queue's get() method, which - then returns its connection to the Queue via the the put() method, + then returns its connection to the Queue via the put() method, causing a reentrant hang unless threading.RLock is used. .. change:: diff --git a/doc/build/changelog/changelog_03.rst b/doc/build/changelog/changelog_03.rst index 6cecaa5cd1..05e10e6649 100644 --- a/doc/build/changelog/changelog_03.rst +++ b/doc/build/changelog/changelog_03.rst @@ -2091,7 +2091,7 @@ :tickets: added a mutex to the mapper compilation step. ive been reluctant to add any - kind of threading anything to SA but this is one spot that its its really + kind of threading anything to SA but this is one spot that its really needed since mappers are typically "global", and while their state does not change during normal operation, the initial compilation step does modify internal state significantly, and this step usually occurs not at diff --git a/doc/build/changelog/changelog_04.rst b/doc/build/changelog/changelog_04.rst index 0064328641..61ea28c119 100644 --- a/doc/build/changelog/changelog_04.rst +++ b/doc/build/changelog/changelog_04.rst @@ -2034,7 +2034,7 @@ new synonym() behavior: an attribute will be placed on the mapped class, if one does not exist already, in all cases. if a property already exists on the class, the synonym will decorate the property - with the appropriate comparison operators so that it can be used in in + with the appropriate comparison operators so that it can be used in column expressions just like any other mapped attribute (i.e. usable in filter(), etc.) the "proxy=True" flag is deprecated and no longer means anything. Additionally, the flag "map_column=True" will automatically @@ -2870,7 +2870,7 @@ :tickets: PG reflection, upon seeing the default schema name being used explicitly - as the "schema" argument in a Table, will assume that this is the the + as the "schema" argument in a Table, will assume that this is the user's desired convention, and will explicitly set the "schema" argument in foreign-key-related reflected tables, thus making them match only with Table constructors that also use the explicit "schema" argument @@ -2927,7 +2927,7 @@ :tickets: 810 Fixed breakage with postgres and multiple two-phase transactions. Two-phase - commits and and rollbacks didn't automatically end up with a new transaction + commits and rollbacks didn't automatically end up with a new transaction as the usual dbapi commits/rollbacks do. .. change:: diff --git a/doc/build/changelog/changelog_06.rst b/doc/build/changelog/changelog_06.rst index 0d926c3e4c..18d61019aa 100644 --- a/doc/build/changelog/changelog_06.rst +++ b/doc/build/changelog/changelog_06.rst @@ -943,7 +943,7 @@ :tickets: 1953 The cx_oracle "decimal detection" logic, which takes place - for for result set columns with ambiguous numeric characteristics, + for result set columns with ambiguous numeric characteristics, now uses the decimal point character determined by the locale/ NLS_LANG setting, using an on-first-connect detection of this character. cx_oracle 5.0.3 or greater is also required @@ -2851,7 +2851,7 @@ :tickets: 1071 Postgresql now reflects sequence names associated with - SERIAL columns correctly, after the name of of the sequence + SERIAL columns correctly, after the name of the sequence has been changed. Thanks to Kumar McMillan for the patch. .. change:: diff --git a/doc/build/changelog/changelog_07.rst b/doc/build/changelog/changelog_07.rst index dd578ceda6..68e03a2e25 100644 --- a/doc/build/changelog/changelog_07.rst +++ b/doc/build/changelog/changelog_07.rst @@ -9,15 +9,15 @@ .. change:: :tags: bug, engine :tickets: 2851 - :versions: 0.8.3, 0.9.0 + :versions: 0.8.3, 0.9.0b1 - The regexp used by the :func:`~.sqlalchemy.engine.url.make_url` function now parses + The regexp used by the :func:`~sqlalchemy.engine.url.make_url` function now parses ipv6 addresses, e.g. surrounded by brackets. .. change:: :tags: bug, orm :tickets: 2807 - :versions: 0.8.3, 0.9.0 + :versions: 0.8.3, 0.9.0b1 Fixed bug where list instrumentation would fail to represent a setslice of ``[0:0]`` correctly, which in particular could occur @@ -28,7 +28,7 @@ .. change:: :tags: bug, sql :tickets: 2801 - :versions: 0.8.3, 0.9.0 + :versions: 0.8.3, 0.9.0b1 Fixed regression dating back to 0.7.9 whereby the name of a CTE might not be properly quoted if it was referred to in multiple FROM clauses. @@ -36,7 +36,7 @@ .. change:: :tags: mysql, bug :tickets: 2791 - :versions: 0.8.3, 0.9.0 + :versions: 0.8.3, 0.9.0b1 Updates to MySQL reserved words for versions 5.5, 5.6, courtesy Hanno Schlichting. @@ -44,7 +44,7 @@ .. change:: :tags: sql, bug, cte :tickets: 2783 - :versions: 0.8.3, 0.9.0 + :versions: 0.8.3, 0.9.0b1 Fixed bug in common table expression system where if the CTE were used only as an ``alias()`` construct, it would not render using the @@ -53,7 +53,7 @@ .. change:: :tags: bug, sql :tickets: 2784 - :versions: 0.8.3, 0.9.0 + :versions: 0.8.3, 0.9.0b1 Fixed bug in :class:`.CheckConstraint` DDL where the "quote" flag from a :class:`.Column` object would not be propagated. @@ -128,7 +128,7 @@ :version: 0.7.10 :released: Thu Feb 7 2013 - .. change: + .. change:: :tags: sql, mysql, gae :tickets: 2649 @@ -155,25 +155,6 @@ :class:`.Column` had both a foreign key as well as an alternate ".key" name for the column. - .. change:: - :tags: engine, bug - :tickets: 2604 - - Fixed :meth:`.MetaData.reflect` to correctly use - the given :class:`.Connection`, if given, without - opening a second connection from that connection's - :class:`.Engine`. - - .. change:: - :tags: mssql, bug - :tickets:2607 - - Fixed bug whereby using "key" with Column - in conjunction with "schema" for the owning - Table would fail to locate result rows due - to the MSSQL dialect's "schema rendering" - logic's failure to take .key into account. - .. change:: :tags: mssql, bug :tickets: 2638 @@ -187,7 +168,7 @@ :tickets: 2650 Fixed potential memory leak which could occur if an - arbitrary number of :func:`.sessionmaker` objects + arbitrary number of :class:`.sessionmaker` objects were created. The anonymous subclass created by the sessionmaker, when dereferenced, would not be garbage collected due to remaining class-level references from the @@ -1463,10 +1444,10 @@ :tickets: 2361 Dialect-specific compilers now raise - CompileException for all type/statement compilation + CompileError for all type/statement compilation issues, instead of InvalidRequestError or ArgumentError. The DDL for CREATE TABLE will re-raise - CompileExceptions to include table/column information + CompileError to include table/column information for the problematic column. .. change:: @@ -1966,7 +1947,7 @@ :tickets: 1679 a "has_schema" method has been implemented - on dialect, but only works on Postgresql so far. + on dialect, but only works on Postgresql so far. Courtesy Manlio Perillo. .. change:: -- 2.47.2