Hello community, here is the log from the commit of package python3-SQLAlchemy for openSUSE:Factory checked in at 2016-11-12 13:01:16 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python3-SQLAlchemy (Old) and /work/SRC/openSUSE:Factory/.python3-SQLAlchemy.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Package is "python3-SQLAlchemy" Changes: -------- --- /work/SRC/openSUSE:Factory/python3-SQLAlchemy/python3-SQLAlchemy.changes 2016-10-22 13:23:23.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.python3-SQLAlchemy.new/python3-SQLAlchemy.changes 2016-11-12 13:01:18.000000000 +0100 @@ -1,0 +2,40 @@ +Thu Oct 27 16:05:01 UTC 2016 - arun@gmx.de + +- update to version 1.1.3: + * orm + + [orm] [bug] Fixed regression caused by #2677 whereby calling + Session.delete() on an object that was already flushed as + deleted in that session would fail to set up the object in the + identity map (or reject the object), causing flush errors as the + object were in a state not accommodated by the unit of work. The + pre-1.1 behavior in this case has been restored, which is that + the object is put back into the identity map so that the DELETE + statement will be attempted again, which emits a warning that + the number of expected rows was not matched (unless the row were + restored outside of the session). + + [orm] [bug] Fixed regression where some Query methods like + Query.update() and others would fail if the Query were against a + series of mapped columns, rather than the mapped entity as a + whole. + * sql + + [sql] [bug] Fixed bug involving new value translation and + validation feature in Enum whereby using the enum object in a + string concatenation would maintain the Enum type as the type of + the expression overall, producing missing lookups. A string + concatenation against an Enum-typed column now uses String as + the datatype of the expression itself. + + [sql] [bug] Fixed regression which occurred as a side effect of + #2919, which in the less typical case of a user-defined + TypeDecorator that was also itself an instance of SchemaType + (rather than the implementation being such) would cause the + column attachment events to be skipped for the type itself. + * postgresql + + [postgresql] [bug] Postgresql table reflection will ensure that + the Column.autoincrement flag is set to False when reflecting a + primary key column that is not of an Integer datatype, even if + the default is related to an integer-generating sequence. This + can happen if a column is created as SERIAL and the datatype is + changed. The autoincrement flag can only be True if the datatype + is of integer affinity in the 1.1 series. + +------------------------------------------------------------------- Old: ---- SQLAlchemy-1.1.2.tar.gz New: ---- SQLAlchemy-1.1.3.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python3-SQLAlchemy.spec ++++++ --- /var/tmp/diff_new_pack.NORmJn/_old 2016-11-12 13:01:19.000000000 +0100 +++ /var/tmp/diff_new_pack.NORmJn/_new 2016-11-12 13:01:19.000000000 +0100 @@ -17,7 +17,7 @@ Name: python3-SQLAlchemy -Version: 1.1.2 +Version: 1.1.3 Release: 0 Url: http://www.sqlalchemy.org Summary: Database Abstraction Library ++++++ SQLAlchemy-1.1.2.tar.gz -> SQLAlchemy-1.1.3.tar.gz ++++++ ++++ 5224 lines of diff (skipped)