Hello,
thanks to the hard work of Domen Kožar and Chris Withers I can
announce the new release 0.6.1 of sqlalchemy-migrate today. The
release is available at PyPI and our project page [1].
Release Notes for sqlalchemy-migrate 0.6.1
==========================================
Changes since 0.6.0
- -------------------
Features
********
- - implemented column adding when foreign keys are present for sqlite
- - implemented columns adding with unique constraints for sqlite
- - implemented adding unique and foreign key constraints to columns for
sqlite
Fixed bugs
**********
- - updated tests for Python 2.7
- - repository keyword in api.version_control can also be unicode
- - added if main condition for manage.py script
- - make migrate.changeset.constraint.ForeignKeyConstraint.autoname
work with SQLAlchemy 0.5 and 0.6
- - fixed case sensitivity in setup.py dependencies
- - moved migrate.changeset.exceptions and
migrate.versioning.exceptions to migrate.exceptions
- - cleared up test output and improved testing of deprecation
warnings.
- - some documentation fixes
- - fixed syntax error in genmodel.py (issue 107)
- - fixed bug with column dropping in sqlite (issue 96)
- - fixed bug with column dropping involving foreign keys
- - fixed bug that prevented non-unique indexes being created
(issue 94)
- - fixed bug when dropping columns with unique constraints in sqlite
- - rewrite of the schema diff internals, now supporting column
differences in additon to missing columns and tables.
- - fixed bug when passing empty list in
migrate.versioning.shell.main failed
Help Wanted
- -----------
- - We need active users of Firebird to continue support for this
database
- - Triage bugs on the issue tracker [2] and provide patches
- - Improve documentation, provide useful best practice documents, FAQ
and more
- - If Microsoft SQL Server support is desired we need access to an
appropriate System and a continuous integration setup (i.e. Jenkins
CI) running on such a system
Credits
- -------
Thanks for all contributors who made the release possible, especially:
* Domen Kožar
* Chris Withers
Thanks to all bug reporters and people giving valuable feedback to the
migrate-users list and in #sqlalchemy-migrate on IRC.
[1] http://code.google.com/p/sqlalchemy-migrate/
[2] http://code.google.com/p/sqlalchemy-migrate/issues/list
Best Regards,
Jan Dittberner
- --
Jan Dittberner - Debian Developer, Software Architect
GPG-key: 4096R/558FB8DD 2009-05-10
B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD
http://www.dittberner.info/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBCAAGBQJNVaD8AAoJEKc+AFVVj7jdpRkP/39ueIdR+4bHzaDl0NDU/XNl
Ns7gmR+Xf+mqmM8RS9KX+PrfuGTmKoLQeCy0sEZNhKfn+syPFfcOAPqhc3soiYPj
H3XjkCM0mtScwQ5eRBKNpQvvyg0rWQMhVNi7aqMF8nJkceA7Cdt5+SlRkN9fYbKl
dkR3FkeUr8ALYZi0/5nla5s7ScQw8JiyvD0G3n1Xlh2bNPdwaxJ6oriJMJe2mS0k
EXE/v2XkPKsuePCTj4vWNWe2ZNwBsUOmk0Xq+ZTKMIjv4dNM8uHOzWHmvkYSob7v
oo3HDyXvTo3aqRS4UL5M2c76L6pSsZuQnijh3l6ugujw6etCDwvU5Zkcqafq6+8o
ooCzpmNI1zppH74zYoBqxoVQR2kFEoQeiU2f2rUSZHN3rOrphNdH2qPC8s6U8wwD
FRIrSyfjqn4Ov/PVsVQKNSWiqU7H/+AcSYI04WMAQFTQWPwmPBnvMtnpgYBECxMh
XgahLKfptiMyM0SPmRz2Fj+qH7Azov50JWHnAysZmSN9/cDgG99owl9clT/9vssl
NnoryVIjiwbUGG+vN5wWNOu4dPIoHCrQpqgCD+HOA4qhyhQsaOc2EZ5SBz4j7jyU
KL7otPNYxE0w9T103nh6aqxw2olXSYRzVDfBlKAz3VXTQOaJbShhsg2NcrZlJMqC
MmQSSv7dVgKFaXHXJqqO
=dfW2
-----END PGP SIGNATURE-----