Changelog for python3-SQLAlchemy-doc-1.1.5-5.3.x86_64.rpm :

* Fri Feb 03 2017 arunAATTgmx.de- specfile:
* update copyright year- update to version 1.1.5:
* orm + [orm] [bug] Fixed bug involving joined eager loading against multiple entities when polymorphic inheritance is also in use which would throw “‘NoneType’ object has no attribute ‘isa’”. The issue was introduced by the fix for #3611. + [orm] [bug] Fixed bug in subquery loading where an object encountered as an “existing” row, e.g. already loaded from a different path in the same query, would not invoke subquery loaders for unloaded attributes that specified this loading. This issue is in the same area as that of #3431, #3811 which involved similar issues with joined loading. + [orm] [bug] The Session.no_autoflush context manager now ensures that the autoflush flag is reset within a “finally” block, so that if an exception is raised within the block, the state still resets appropriately. Pull request courtesy Emin Arakelian. + [orm] [bug] Fixed bug where the single-table inheritance query criteria would not be inserted into the query in the case that the Bundle construct were used as the selection criteria. + [orm] [bug] Fixed bug related to #3177, where a UNION or other set operation emitted by a Query would apply “single-inheritance” criteria to the outside of the union (also referencing the wrong selectable), even though this criteria is now expected to be already present on the inside subqueries. The single-inheritance criteria is now omitted once union() or another set operation is called against Query in the same way as Query.from_self().
* engine + [engine] [bug] The “extend_existing” option of Table reflection would cause indexes and constraints to be doubled up in the case that the parameter were used with MetaData.reflect() (as the automap extension does) due to tables being reflected both within the foreign key path as well as directly. A new de-duplicating set is passed through within the MetaData.reflect() sequence to prevent double reflection in this way.
* sql + [sql] [bug] Fixed bug originally introduced in 0.9 via #1068 where order_by() would order by the label name based on name alone, that is, even if the labeled expression were not at all the same expression otherwise present, implicitly or explicitly, in the selectable. The logic that orders by label now ensures that the labeled expression is related to the one that resolves to that name before ordering by the label name; additionally, the name has to resolve to an actual label explicit in the expression elsewhere, not just a column name. This logic is carefully kept separate from the order by(textual name) feature that has a slightly different purpose. + [sql] [bug] Fixed 1.1 regression where “import
*” would not work for sqlalchemy.sql.expression, due to mis-spelled “any_” and “all_” functions. + [sql] [bug] The engine URL embedded in the exception for “could not reflect” in MetaData.reflect() now conceals the password; also the __repr__ for TLEngine now acts like that of Engine, concealing the URL password. Pull request courtesy Valery Yundin. + [sql] [bug] Fixed issue in Variant where the “right hand coercion” logic, inherited from TypeDecorator, would coerce the right-hand side into the Variant itself, rather than what the default type for the Variant would do. In the case of Variant, we want the type to act mostly like the base type so the default logic of TypeDecorator is now overridden to fall back to the underlying wrapped type’s logic. Is mostly relevant for JSON at the moment. + [sql] [bg] Fixed bug where literal_binds compiler flag was not honored by the Insert construct for the “multiple values” feature; the subsequent values are now rendered as literals.
* postgresql + [postgresql] [bug] Fixed bug in new “ON CONFLICT DO UPDATE” feature where the “set” values for the UPDATE clause would not be subject to type-level processing, as normally takes effect to handle both user-defined type level conversions as well as dialect-required conversions, such as those required for JSON datatypes. Additionally, clarified that the keys in the set_ dictionary should match the “key” of the column, if distinct from the column name. A warning is emitted for remaining column names that don’t match column keys; for compatibility reasons, these are emitted as they were previously. + [postgresql] [bug] The postgresql.TIME and postgresql.TIMESTAMP datatypes now support a setting of zero for “precision”; previously a zero would be ignored. Pull request courtesy Ionuț Ciocîrlan.
* mysql + [mysql] [feature] Added a new parameter mysql_prefix supported by the Index construct, allows specification of MySQL-specific prefixes such as “FULLTEXT”. Pull request courtesy Joseph Schorr. + [mysql] [bug] The MySQL dialect now will not warn when a reflected column has a “COMMENT” keyword on it, but note however the comment is not yet reflected; this is on the roadmap for a future release. Pull request courtesy Lele Long.
* mssql + [mssql] [bug] Fixed bug where SQL Server dialects would attempt to select the last row identity for an INSERT from SELECT, failing in the case when the SELECT has no rows. For such a statement, the inline flag is set to True indicating no last primary key should be fetched.
* oracle + [oracle] [bug] [postgresql] Fixed bug where an INSERT from SELECT where the source table contains an autoincrementing Sequence would fail to compile correctly. + [oracle] [bug] Fixed bug where the “COMPRESSION” keyword was used in the ALL_TABLES query on Oracle 9.2; even though Oracle docs state table compression was introduced in 9i, the actual column is not present until 10.1.
* firebird + [firebird] [bug] Ported the fix for Oracle quoted-lowercase names to Firebird, so that a table name that is quoted as lower case can be reflected properly including when the table name comes from the get_table_names() inspection function.
* misc + [bug] [py3k] Fixed Python 3.6 DeprecationWarnings related to escaped strings without the ‘r’ modifier, and added test coverage for Python 3.6. + [bug] [examples] Fixed two issues with the versioned_history example, one is that the history table now gets autoincrement=False to avoid 1.1’s new errors regarding composite primary keys with autoincrement; the other is that the sqlite_autoincrement flag is now used to ensure on SQLite, unique identifiers are used for the lifespan of a table even if some rows are deleted. Pull request courtesy Carlos García Montoro.
* Sat Nov 19 2016 arunAATTgmx.de- update to version 1.1.4:
* orm + [orm] [bug] Fixed bug in Session.bulk_update_mappings() where an alternate-named primary key attribute would not track properly into the UPDATE statement. + [orm] [bug] Fixed bug in Session.bulk_save() where an UPDATE would not function correctly in conjunction with a mapping that implements a version id counter. + [orm] [bug] Fixed bug where the Mapper.attrs, Mapper.all_orm_descriptors and other derived attributes would fail to refresh when mapper properties or other ORM constructs were added to the mapper/class after these accessors were first called. + [orm] [bug] Fixed regression in collections due to #3457 whereby deserialize during pickle or deepcopy would fail to establish all attributes of an ORM collection, causing further mutation operations to fail. + [orm] [bug] Fixed long-standing bug where the “noload” relationship loading strategy would cause backrefs and/or back_populates options to be ignored.
* engine + [engine] [bug] Removed long-broken “default_schema_name()” method from Connection. This method was left over from a very old version and was non-working (e.g. would raise). Pull request courtesy Benjamin Dopplinger.
* sql + [sql] [bug] Fixed bug where newly added warning for primary key on insert w/o autoincrement setting (see The .autoincrement directive is no longer implicitly enabled for a composite primary key column) would fail to emit correctly when invoked upon a lower-case table() construct.
* postgresql + [postgresql] [bug] Fixed regression caused by the fix in #3807 (version 1.1.0) where we ensured that the tablename was qualified in the WHERE clause of the DO UPDATE portion of PostgreSQL’s ON CONFLICT, however you cannot put the table name in the WHERE clause in the actual ON CONFLICT itself. This was an incorrect assumption, so that portion of the change in #3807 is rolled back.
* mysql + [mysql] [feature] Added support for server side cursors to the mysqlclient and pymysql dialects. This feature is available via the Connection.execution_options.stream_results flag as well as the server_side_cursors=True dialect argument in the same way that it has been for psycopg2 on Postgresql. Pull request courtesy Roman Podoliaka. + [mysql] [bug] MySQL’s native ENUM type supports any non-valid value being sent, and in response will return a blank string. A hardcoded rule to check for “is returning the blank string” has been added to the MySQL implementation for ENUM so that this blank string is returned to the application rather than being rejected as a non-valid value. Note that if your MySQL enum is linking values to objects, you still get the blank string back.
* sqlite + [sqlite] [bug] Added quotes to the PRAGMA directives in the pysqlcipher dialect to support additional cipher arguments appropriately. Pull request courtesy Kevin Jurczyk. + [sqlite] [bug] [py3k] Added an optional import for the pysqlcipher3 DBAPI when using the pysqlcipher dialect. This package will attempt to be imported if the Python-2 only pysqlcipher DBAPI is non-present. Pull request courtesy Kevin Jurczyk.
* mssql + [mssql] [bug] Fixed bug in pyodbc dialect (as well as in the mostly non-working adodbapi dialect) whereby a semicolon present in the password or username fields could be interpreted as a separator for another token; the values are now quoted when semicolons are present.
* Thu Oct 27 2016 arunAATTgmx.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.
* Fri Oct 21 2016 arunAATTgmx.de- update to version 1.1.2:
* orm + [orm] [bug] Fixed bug involving the rule to disable a joined collection eager loader on the other side of a many-to-one lazy loader, first added in #1495, where the rule would fail if the parent object had some other lazyloader-bound query options associated with it. + [orm] [bug] Fixed self-referential entity, deferred column loading issue in a similar style as that of #3431, #3811 where an entity is present in multiple positions within the row due to self-referential eager loading; when the deferred loader only applies to one of the paths, the “present” column loader will now override the deferred non- load for that entity regardless of row ordering.
* sql + [sql] [bug] Fixed a regression caused by a newly added function that performs the “wrap callable” function of sql DefaultGenerator objects, an attribute error raised for __module__ when the default callable was a functools.partial or other object that doesn’t have a __module__ attribute. + [sql] [bug] [postgresql] Fixed regression in Enum type where event handlers were not transferred in the case of the type object being copied, due to a conflicting copy() method added as part of #3250. This copy occurs normally in situations when the column is copied, such as in tometadata() or when using declarative mixins with columns. The event handler not being present would impact the constraint being created for a non-native enumerated type, but more critically the ENUM object on the PostgreSQL backend.
* postgresql + [postgresql] [bug] [sql] Changed the naming convention used when generating bound parameters for a multi-VALUES insert statement, so that the numbered parameter names don’t conflict with the anonymized parameters of a WHERE clause, as is now common in a PostgreSQL ON CONFLICT construct.
* Wed Oct 12 2016 arunAATTgmx.de- update to version 1.1.1: (long changelog for 1.1.1, 1.1 and 1.0.16, see http://docs.sqlalchemy.org/en/latest/changelog/changelog_11.html for details)
* Thu Sep 15 2016 toddrme2178AATTgmail.com- Update to 1.0.15:
* See http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html#change-1.0.15 http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html#change-1.0.14
* Mon May 23 2016 toddrme2178AATTgmail.com- update to version 1.0.13: + orm
* [orm] [bug] Fixed bug in “evaluate” strategy of Query.update() and Query.delete() which would fail to accommodate a bound parameter with a “callable” value, as which occurs when filtering by a many-to-one equality expression along a relationship.
* [orm] [bug] Fixed bug whereby the event listeners used for backrefs could be inadvertently applied multiple times, when using a deep class inheritance hierarchy in conjunction with mutiple mapper configuration steps.
* [orm] [bug] Fixed bug whereby passing a text() construct to the Query.group_by() method would raise an error, instead of intepreting the object as a SQL fragment.
* [orm] [bug] Anonymous labeling is applied to a func construct that is passed to 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.
* [orm] [bug] Fixed regression appearing in the 1.0 series in ORM loading where the exception raised for an expected column missing would incorrectly be a NoneType error, rather than the expected NoSuchColumnError. + sql
* [sql] [bug] Fixed bug where when using case_sensitive=False with an Engine, the result set would fail to correctly accomodate for duplicate column names in the result set, causing an error when the statement is executed in 1.0, and preventing the “ambiguous column” exception from functioning in 1.1.
* [sql] [bug] Fixed bug where the negation of an EXISTS expression would not be properly typed as boolean in the result, and also would fail to be anonymously aliased in a SELECT list as is the case with a non-negated EXISTS construct.
* [sql] [bug] Fixed bug where “unconsumed column names” exception would fail to be raised in the case where Insert.values() were called with a list of parameter mappings, instead of a single mapping of parameters. Pull request courtesy Athena Yao. + postgresql
* [postgresql] [bug] Added disconnect detection support for the error string “SSL error: decryption failed or bad record mac”. Pull request courtesy Iuri de Silvio. + mssql
* [mssql] [bug] Fixed bug where by ROW_NUMBER OVER clause applied for OFFSET selects in SQL Server would inappropriately substitute a plain column from the local statement that overlaps with a label name used by the ORDER BY criteria of the statement.
* [mssql] [bug] [oracle] Fixed regression appearing in the 1.0 series which would cause the Oracle and SQL Server dialects to incorrectly account for result set columns when these dialects would wrap a SELECT in a subquery in order to provide LIMIT/OFFSET behavior, and the original SELECT statement referred to the same column multiple times, such as a column and a label of that same column. This issue is related to #3658 in that when the error occurred, it would also cause a NoneType error, rather than reporting that it couldn’t locate a column. + oracle
* [oracle] [bug] Fixed a bug in the cx_Oracle connect process that caused a TypeError when the either the user, password or dsn was empty. This prevented external authentication to Oracle databases, and prevented connecting to the default dsn. The connect string oracle:// now logs into the default dsn using the Operating System username, equivalent to connecting using ‘/’ with sqlplus.
* [oracle] [bug] Fixed a bug in the result proxy used mainly by Oracle when binary and other LOB types are in play, such that when query / statement caching were used, the type-level result processors, notably that required by the binary type itself but also any other processor, would become lost after the first run of the statement due to it being removed from the cached result metadata. + misc
* [bug] [examples] Changed the “directed graph” example to no longer consider integer identifiers of nodes as significant; the “higher” / “lower” references now allow mutual edges in both directions.
* [bug] [py3k] Fixed bug in “to_list” conversion where a single bytes object would be turned into a list of individual characters. This would impact among other things using the Query.get() method on a primary key that’s a bytes object.¶
* Sun May 08 2016 arunAATTgmx.de- specfile:
* changed to https for source url
* updated source url to files.pythonhosted.org
* Fri Mar 11 2016 toddrme2178AATTgmail.com- Really removed patch fix_joins_and_union_for_sqlite_3.10.0.patch, included upstream
* Wed Feb 17 2016 arunAATTgmx.de- specfile:
* removed patch fix_joins_and_union_for_sqlite_3.10.0.patch, included upstream- update to version 1.0.12:
* orm + [orm] [bug] Fixed bug in Session.merge() where an object with a composite 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. + [orm] [bug] Fixed regression since 0.9 where the 0.9 style loader options system failed to accommodate for multiple undefer_group() loader options in a single query. Multiple undefer_group() options will now be taken into account even against the same entity.
* engine + [engine] [bug] [mysql] Revisiting #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 Session and 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.
* sql + [sql] [bug] Fixed issue where the “literal_binds” flag was not propagated for expression.insert(), expression.update() or expression.delete() constructs when compiled to string SQL. Pull request courtesy Tim Tate. + [sql] [bug] Fixed issue where inadvertent use of the Python __contains__ 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. + [sql] [bug] Fixed bug in Table metadata construct which appeared around the 0.9 series where adding columns to a Table that was unpickled would fail to correctly establish the 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.
* postgresql + [postgresql] [bug] Fixed bug in expression.text() construct where a double-colon expression would not escape properly, e.g. some\\:\\:expr, as is most commonly required when rendering Postgresql-style CAST expressions.
* mssql + [mssql] [bug] Fixed the syntax of the extract() function when used on MSSQL against a datetime value; the quotes around the keyword are removed. Pull request courtesy Guillaume Doumenc. + [mssql] [bug] [firebird] Fixed 1.0 regression where the eager fetch of cursor.rowcount was no longer called for an UPDATE or DELETE statement emitted via plain text or via the text() construct, affecting those drivers that erase cursor.rowcount once the cursor is closed such as SQL Server ODBC and Firebird drivers.
* oracle + [oracle] [bug] [jython] Fixed a small issue in the Jython Oracle compiler involving the rendering of “RETURNING” which allows this currently unsupported/untested dialect to work rudimentally with the 1.0 series. Pull request courtesy Carlos Rivas.
* misc + [bug] [py3k] Fixed bug where some exception re-raise scenarios would attach the exception to itself as the “cause”; while the Python 3 interpreter is OK with this, it could cause endless loops in iPython.
* Fri Feb 12 2016 toddrme2178AATTgmail.com- Add fix_joins_and_union_for_sqlite_3.10.0.patch to remove a workaround for an earlier version of SQLite. The issue the workaround was for was fixed in SQLite 3.10.0, which causes problems for that version and later. This patch removes the workaround when it is not needed. This patch should be in the next release. See: https://bitbucket.org/zzzeek/sqlalchemy/issues/3633/
* Thu Jan 07 2016 toddrme2178AATTgmail.com- update to version 1.0.11:
* see changelog at http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html#change-1.0.11- Tests fail with python3-buildservice-tweak
* Mon Dec 14 2015 arunAATTgmx.de- update to version 1.0.10:
* see changelog at http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html#change-1.0.10
* Sun Nov 01 2015 arunAATTgmx.de- update to version 1.0.9:
* see changelog at http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html#change-1.0.9
* Sun Oct 04 2015 arunAATTgmx.de- update to version 1.0.8:
* [engine] [bug] Fixed critical issue whereby the pool \"checkout\" event handler may be called against a stale connection without the \"connect\" event handler having been called, in the case where the pool attempted to reconnect after being invalidated and failed; the stale connection would remain present and would be used on a subsequent attempt. This issue has a greater impact in the 1.0 series subsequent to 1.0.2, as it also delivers a blanked-out .info dictionary to the event handler; prior to 1.0.2 the .info dictionary is still the previous one. This change is also backported to: 0.9.11 References: #3497
* [sqlite] [bug] Fixed bug in SQLite dialect where reflection of UNIQUE constraints that included non-alphabetic characters in the names, like dots or spaces, would not be reflected with their name. This change is also backported to: 0.9.10 References: #3495
* [misc] [bug] Fixed an issue where a particular base class within utils didn’t implement __slots__, and therefore meant all subclasses of that class didn’t either, negating the rationale for __slots__ to be in use. Didn’t cause any issue except on IronPython which apparently does not implement __slots__ behavior compatibly with cPython. References: #3494
* Tue Jul 21 2015 arunAATTgmx.de- update to version 1.0.7:
* see http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html#change-1.0.7
* Mon Jul 13 2015 arunAATTgmx.de- update to version 1.0.6:
* see http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html#change-1.0.6
* Sat Jun 13 2015 arunAATTgmx.de- update to version 1.0.5:
* see http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html#change-1.0.5
* Sat May 09 2015 arunAATTgmx.de- update to version 1.0.4:
* see http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html#change-1.0.4
* Sat May 02 2015 arunAATTgmx.de- update to version 1.0.3:
* see http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html#change-1.0.3
* Sat Apr 25 2015 arunAATTgmx.de- update to version 1.0.2:
* see http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html#change-1.0.2
* Fri Apr 24 2015 arunAATTgmx.de- update to version 1.0.1: see http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html#change-1.0.1 for detailed list of changes
* Sun Apr 19 2015 arunAATTgmx.de- update to version 1.0.0:
* long list of changes, see http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html#change-1.0.0
* Wed Mar 11 2015 arunAATTgmx.de- update to version 0.9.9:
* long changelog, see http://docs.sqlalchemy.org/en/latest/changelog/changelog_09.html for details
* Sat Jan 17 2015 arunAATTgmx.de- specfile:
* update copyright year
* Drop SQLAlchemy-import-logging-handlers.patch: + test_mapper.py got fixed upstream + test_execute.py doesn\'t use logging anymore
* no more README.py3k. removed it from spec file
* remove noarch
* changed sitelib to sitearch in %files section
* removed some 2to3 conversion that is not needed anymore- update to version 0.9.8: Many changes (a few thousand lines), see links below for complete list http://docs.sqlalchemy.org/en/latest/changelog/changelog_09.html http://docs.sqlalchemy.org/en/latest/changelog/changelog_08.html
* Fri Nov 01 2013 p.drouandAATTgmail.com- Update to version 0.8.3 + See http://docs.sqlalchemy.org/en/latest/changelog/changelog_08.html#change-0.8.3- Fix build on Factory
* Sat Oct 26 2013 p.drouandAATTgmail.com- Update to version 0.8.2 + Too numuch changes See http://docs.sqlalchemy.org/en/latest/changelog/changelog_08.html#change-0.8.2- Don\'t apply SQLAlchemy-import-logging-handlers.patch; sounds fixed by upstream
* Thu Jul 18 2013 speilickeAATTsuse.com- Add SQLAlchemy-import-logging-handlers.patch: Fix missing imports during test runs
* Tue Jul 16 2013 speilickeAATTsuse.com- Run 2to3
* Fri Mar 08 2013 larsAATTlinux-schulserver.de- update to 0.7.10:
* orm + [bug] Fixed Session accounting bug whereby replacing a deleted object in the identity map with another object of the same primary key would raise a \"conflicting state\" error on rollback(), if the replaced primary key were established either via non-unitofwork-established INSERT statement or by primary key switch of another instance. [ticket:2583]
* oracle + [bug] changed the list of cx_oracle types that are excluded from the setinputsizes() step to only include STRING and UNICODE; CLOB and NCLOB are removed. This is to work around cx_oracle behavior which is broken for the executemany() call. In 0.8, this same change is applied however it is also configurable via the exclude_setinputsizes argument. [ticket:2561]
* mysql + [feature] Added \"raise_on_warnings\" flag to OurSQL dialect. [ticket:2523] + [feature] Added \"read_timeout\" flag to MySQLdb dialect. [ticket:2554]
* Wed Dec 19 2012 saschpeAATTsuse.de- The doc package is noarch
* Thu Nov 22 2012 toddrme2178AATTgmail.com- Remove openSUSE 11.4 spec file workarounds
* Fri May 25 2012 toddrme2178AATTgmail.com- Fix building on openSUSE 11.4- spec file cleanups
* Wed May 23 2012 highwaystar.ruAATTgmail.com- python3-SQLAlchemy package added