From Fedora Project Wiki
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
* <code>Column.alter</code> does not accept <code>current_name</code> anymore, it extracts name from the old column. | * <code>Column.alter</code> does not accept <code>current_name</code> anymore, it extracts name from the old column. | ||
For complete list of changes refer to the [http://packages.python.org/sqlalchemy-migrate/changelog.htm changelog] | For complete list of changes refer to the [http://packages.python.org/sqlalchemy-migrate/changelog.htm changelog] | ||
=== boost === | |||
* Boost 1.44.0 Release Notes (as of June, 2010, not yet delivered) | |||
http://www.boost.org/users/history/version_1_44_0 | |||
* Boost 1.43.0 Release Notes | |||
http://www.boost.org/users/history/version_1_43_0 | |||
* Boost 1.42.0 Release Notes | |||
http://www.boost.org/users/history/version_1_42_0 | |||
Revision as of 20:41, 28 August 2010
python-migrate
python-migrate was updated to version 0.6. Support for SQLAlchemy 0.6 and Firebird database, custom templates and use of python logging are among many new features. New version also introduces some backwards incompatible changes:
api.test()and schema comparison functions now all accept url as first parameter and repository as second.- python upgrade/downgrade scripts do not import migrate_engine magically, but recieve engine as the only parameter to function (eg. def
upgrade(migrate_engine):) Column.alterdoes not acceptcurrent_nameanymore, it extracts name from the old column.
For complete list of changes refer to the changelog
boost
- Boost 1.44.0 Release Notes (as of June, 2010, not yet delivered)
http://www.boost.org/users/history/version_1_44_0
- Boost 1.43.0 Release Notes
http://www.boost.org/users/history/version_1_43_0
- Boost 1.42.0 Release Notes