Hello community,

here is the log from the commit of package python-SQLAlchemy for 
openSUSE:Factory checked in at 2012-11-06 16:22:00
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-SQLAlchemy (Old)
 and      /work/SRC/openSUSE:Factory/.python-SQLAlchemy.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-SQLAlchemy", Maintainer is "[email protected]"

Changes:
--------
--- /work/SRC/openSUSE:Factory/python-SQLAlchemy/python-SQLAlchemy.changes      
2012-05-29 10:36:12.000000000 +0200
+++ /work/SRC/openSUSE:Factory/.python-SQLAlchemy.new/python-SQLAlchemy.changes 
2012-11-06 16:22:02.000000000 +0100
@@ -1,0 +2,223 @@
+Fri Nov  2 17:53:22 UTC 2012 - [email protected]
+
+- do not require python-pysqlite package.
+- update to 0.7.9:
+
+  *orm
+
+  - [bug] Fixed bug mostly local to new AbstractConcreteBase helper
+    where the "type" attribute from the superclass would not be overridden
+    on the subclass to produce the "reserved for base" error message,
+    instead placing a do-nothing attribute there. This was inconsistent
+    vs. using ConcreteBase as well as all the behavior of classical
+    concrete mappings, where the "type" column from the polymorphic base
+    would be explicitly disabled on subclasses, unless overridden
+    explicitly.
+
+  - [bug] A warning is emitted when lazy='dynamic' is combined with
+    uselist=False. This is an exception raise in 0.8.
+
+  - [bug] Fixed bug whereby user error in related-object assignment could
+    cause recursion overflow if the assignment triggered a backref of the
+    same name as a bi-directional attribute on the incorrect class to the
+    same target. An informative error is raised now.
+
+  - [bug] Fixed bug where incorrect type information would be passed when
+    the ORM would bind the "version" column, when using the "version"
+    feature. Tests courtesy Daniel Miller. [ticket:2539]
+
+  - [bug] Extra logic has been added to the "flush" that occurs within
+    Session.commit(), such that the extra state added by an after_flush()
+    or after_flush_postexec() hook is also flushed in a subsequent flush,
+    before the "commit" completes. Subsequent calls to flush() will
+    continue until the after_flush hooks stop adding new state. An
+    "overflow" counter of 100 is also in place, in the event of a broken
+    after_flush() hook adding new content each time.  [ticket:2566] 
+
+  *engine
+
+  - [feature] Dramatic improvement in memory usage of the event system;
+    instance-level collections are no longer created for a particular type of
+    event until instance-level listeners are established for that
+    event. [ticket:2516] 
+
+  - [bug] Fixed bug whereby a disconnect detect + dispose that occurs when
+    the QueuePool has threads waiting for connections would leave those
+    threads waiting for the duration of the timeout on the old pool (or
+    indefinitely if timeout was disabled). The fix now notifies those
+    waiters with a special exception case and has them move onto the new
+    pool. [ticket:2522]
+
+  - [bug] Added gaerdbms import to mysql/__init__.py, the absense of which
+    was preventing the new GAE dialect from being loaded. [ticket:2529]
+
+  - [bug] Fixed cextension bug whereby the "ambiguous column error" would
+    fail to function properly if the given index were a Column object and
+    not a string. Note there are still some column-targeting issues here
+    which are fixed in 0.8. [ticket:2553]
+
+  - [bug] Fixed the repr() of Enum to include the "name" and "native_enum"
+    flags. Helps Alembic autogenerate. 
+
+  *sql
+
+  - [bug] Fixed the DropIndex construct to support an Index associated with
+    a Table in a remote schema. [ticket:2571] 
+
+  - [bug] Fixed bug in over() construct whereby passing an empty list for
+    either partition_by or order_by, as opposed to None, would fail to
+    generate correctly. Courtesy Gunnlaugur Þór Briem. [ticket:2574] 
+
+  - [bug] Fixed CTE bug whereby positional bound parameters present in the
+    CTEs themselves would corrupt the overall ordering of bound
+    parameters. This primarily affected SQL Server as the platform with
+    positional binds + CTE support. [ticket:2521] 
+
+  - [bug] Fixed more un-intuitivenesses in CTEs which prevented referring
+    to a CTE in a union of itself without it being aliased. CTEs now render
+    uniquely on name, rendering the outermost CTE of a given name only -
+    all other references are rendered just as the name. This even includes
+    other CTE/SELECTs that refer to different versions of the same CTE
+    object, such as a SELECT or a UNION ALL of that SELECT. We are somewhat
+    loosening the usual link between object identity and lexical identity
+    in this case. A true name conflict between two unrelated CTEs now
+    raises an error. 
+
+  - [bug] quoting is applied to the column names inside the WITH RECURSIVE
+    clause of a common table expression according to the quoting rules for
+    the originating Column. [ticket:2512] 
+
+  - [bug] Fixed regression introduced in 0.7.6 whereby the FROM list of a
+    SELECT statement could be incorrect in certain "clone+replace"
+    scenarios. [ticket:2518] 
+
+  - [bug] Fixed bug whereby usage of a UNION or similar inside of an
+    embedded subquery would interfere with result-column targeting, in the
+    case that a result-column had the same ultimate name as a name inside
+    the embedded UNION. [ticket:2552] 
+
+  - [bug] Fixed a regression since 0.6 regarding result-row targeting. It
+    should be possible to use a select() statement with string based
+    columns in it, that is select(['id', 'name']).select_from('mytable'),
+    and have this statement be targetable by Column objects with those
+    names; this is the mechanism by which
+    query(MyClass).from_statement(some_statement) works. At some point the
+    specific case of using select(['id']), which is equivalent to
+    select([literal_column('id')]), stopped working here, so this has been
+    re-instated and of course tested. [ticket:2558] 
+
+  - [bug] Added missing operators is_(), isnot() to the ColumnOperators
+    base, so that these long-available operators are present as methods
+    like all the other operators. [ticket:2544] 
+
+  *postgresql
+
+  - [bug] Columns in reflected primary key constraint are now returned in
+    the order in which the constraint itself defines them, rather than how
+    the table orders them. Courtesy Gunnlaugur Þór Briem.. [ticket:2531] 
+
+  - [bug] Added 'terminating connection' to the list of messages we use to
+    detect a disconnect with PG, which appears to be present in some
+    versions when the server is restarted. [ticket:2570] 
+
+  *mysql
+
+  - [bug] Updated mysqlconnector interface to use updated "client flag" and
+    "charset" APIs, courtesy David McNelis. 
+
+  *sqlite
+
+  - [feature] Added support for the localtimestamp() SQL function
+    implemented in SQLite, courtesy Richard Mitchell. 
+
+  - [bug] Adjusted a very old bugfix which attempted to work around a
+    SQLite issue that itself was "fixed" as of sqlite 3.6.14, regarding
+    quotes surrounding a table name when using the "foreign_key_list"
+    pragma. The fix has been adjusted to not interfere with quotes that are
+    actually in the name of a column or table, to as much a degree as
+    possible; sqlite still doesn't return the correct result for
+    foreign_key_list() if the target table actually has quotes surrounding
+    its name, as part of its name (i.e. """mytable"""). [ticket:2568] 
+
+  - [bug] Adjusted column default reflection code to convert non-string
+    values to string, to accommodate old SQLite versions that don't deliver
+    default info as a string. [ticket:2265] 
+
+  *mssql
+
+  - [bug] Fixed compiler bug whereby using a correlated subquery within an
+    ORDER BY would fail to render correctly if the stament also used
+    LIMIT/OFFSET, due to mis-rendering within the ROW_NUMBER() OVER
+    clause. Fix courtesy sayap [ticket:2538] 
+
+  - [bug] Fixed compiler bug whereby a given select() would be modified if
+    it had an "offset" attribute, causing the construct to not compile
+    correctly a second time. [ticket:2545] 
+
+  - [bug] Fixed bug where reflection of primary key constraint would double
+    up columns if the same constraint/table existed in multiple schemas. 
+
+- update to 0.7.8:
+
+  *orm
+
+  - [feature] The 'objects' argument to flush() is no longer deprecated, as
+    some valid use cases have been identified. 
+
+  - [bug] Fixed bug whereby subqueryload() from a polymorphic mapping to a
+    target would incur a new invocation of the query for each distinct
+    class encountered in the polymorphic result. [ticket:2480] 
+
+  - [bug] Fixed bug in declarative whereby the precedence of columns in a
+    joined-table, composite column (typically for id) would fail to be
+    correct if the columns contained names distinct from their attribute
+    names. This would cause things like primaryjoin conditions made against
+    the entity attributes to be incorrect. Related to as this was supposed
+    to be part of that, this is. [ticket:2491, 1892] 
+
+  - [bug] Fixed identity_key() function which was not accepting a scalar
+    argument for the identity. . [ticket:2508] 
+
+  - [bug] Fixed bug whereby populate_existing option would not propagate to
+    subquery eager loaders. . [ticket:2497] 
+
+  *engine
+
+  - [bug] Fixed memory leak in C version of result proxy whereby DBAPIs
+    which don't deliver pure Python tuples for result rows would fail to
+    decrement refcounts correctly. The most prominently affected DBAPI is
+    pyodbc. [ticket:2489] 
+
+  - [bug] Fixed bug affecting Py3K whereby string positional parameters
+    passed to engine/connection execute() would fail to be interpreted
+    correctly, due to __iter__ being present on Py3K string.. [ticket:2503] 
+
+  *sql
+
+  - [bug] added BIGINT to types.__all__, BIGINT, BINARY, VARBINARY to
++++ 26 more lines (skipped)
++++ between 
/work/SRC/openSUSE:Factory/python-SQLAlchemy/python-SQLAlchemy.changes
++++ and 
/work/SRC/openSUSE:Factory/.python-SQLAlchemy.new/python-SQLAlchemy.changes

Old:
----
  SQLAlchemy-0.7.7.tar.gz

New:
----
  SQLAlchemy-0.7.9.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ python-SQLAlchemy.spec ++++++
--- /var/tmp/diff_new_pack.xp7gLY/_old  2012-11-06 16:22:03.000000000 +0100
+++ /var/tmp/diff_new_pack.xp7gLY/_new  2012-11-06 16:22:03.000000000 +0100
@@ -17,7 +17,7 @@
 
 
 Name:           python-SQLAlchemy
-Version:        0.7.7
+Version:        0.7.9
 Release:        0
 Url:            http://www.sqlalchemy.org
 Summary:        Database Abstraction Library
@@ -28,7 +28,6 @@
 BuildRequires:  python-devel
 BuildRequires:  python-distribute
 BuildRequires:  python-nose
-BuildRequires:  python-pysqlite
 %if 0%{?suse_version}
 %py_requires
 %endif

++++++ python3-SQLAlchemy.spec ++++++
--- /var/tmp/diff_new_pack.xp7gLY/_old  2012-11-06 16:22:03.000000000 +0100
+++ /var/tmp/diff_new_pack.xp7gLY/_new  2012-11-06 16:22:03.000000000 +0100
@@ -17,7 +17,7 @@
 
 
 Name:           python3-SQLAlchemy
-Version:        0.7.7
+Version:        0.7.9
 Release:        0
 Url:            http://www.sqlalchemy.org
 Summary:        Database Abstraction Library
@@ -25,10 +25,10 @@
 Group:          Development/Languages/Python
 Source0:        
http://pypi.python.org/packages/source/S/SQLAlchemy/SQLAlchemy-%{version}.tar.gz
 BuildRoot:      %{_tmppath}/%{name}-%{version}-build
+BuildRequires:  python3-2to3
 BuildRequires:  python3-devel
 BuildRequires:  python3-distribute
 BuildRequires:  python3-nose
-BuildRequires:  python3-2to3
 %if 0%{?suse_version} <= 1140
 %{!?python3_sitelib: %global python3_sitelib %(python3 -c "from 
distutils.sysconfig import get_python_lib; print(get_python_lib())")}
 %{!?py3_ver: %global py3_ver %(python3 -c "import sys; 
version=str(sys.version_info[0]) + '.' + str(sys.version_info[1]); 
print(version)" 2>/dev/null || echo PYTHON-NOT-FOUND)}

++++++ SQLAlchemy-0.7.7.tar.gz -> SQLAlchemy-0.7.9.tar.gz ++++++
++++ 92993 lines of diff (skipped)

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to