The second beta of SQLAlchemy 0.7 is available. This fixes a few regressions reported by users, adds an enhancement to Sequence, and also makes that annoying dictionary in __table_args__ optional. We've had a handful of users report their experiences with 0.7 and the general consensus appears to hover around zero or one issues experienced. Turbogears got hit by the removal of the "sqlalchemy.exception" symbol, someone was dealing with the internals of CursorFairy which has been removed, and the other issues have been addressed in this release. In particular those using the Beaker example should keep an eye on the changes being made and make sure their own apps take advantage of those changes.
SQLAlchemy 0.7 beta2 is available at: http://www.sqlalchemy.org/download.html 0.7.0b2 ======== - orm - Fixed bug whereby Session.merge() would call the load() event with one too few arguments. [ticket:2053] - Added logic which prevents the generation of events from a MapperExtension or SessionExtension from generating do-nothing events for all the methods not overridden. [ticket:2052] - sql - Renamed the EngineEvents event class to ConnectionEvents. As these classes are never accessed directly by end-user code, this strictly is a documentation change for end users. Also simplified how events get linked to engines and connections internally. [ticket:2059] - The Sequence() construct, when passed a MetaData() object via its 'metadata' argument, will be included in CREATE/DROP statements within metadata.create_all() and metadata.drop_all(), including "checkfirst" logic. [ticket:2055] - The Column.references() method now returns True if it has a foreign key referencing the given column exactly, not just it's parent table. [ticket:2064] - postgresql - Fixed regression from 0.6 where SMALLINT and BIGINT types would both generate SERIAL on an integer PK column, instead of SMALLINT and BIGSERIAL [ticket:2065] - ext - Association proxy now has correct behavior for any(), has(), and contains() when proxying a many-to-one scalar attribute to a one-to-many collection (i.e. the reverse of the 'typical' association proxy use case) [ticket:2054] - examples - Beaker example now takes into account 'limit' and 'offset', bind params within embedded FROM clauses (like when you use union() or from_self()) when generating a cache key. - declarative - Fixed regression whereby composite() with Column objects placed inline would fail to initialize. The Column objects can now be inline with the composite() or external and pulled in via name or object ref. [ticket:2058] - the dictionary at the end of the __table_args__ tuple is now optional. [ticket:1468] -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
