[sqlalchemy] [SQLAlchemy-migrate] Add a TSVectorType column to 4 existing tables
Hi !
Does somebody here can tell me something about database migration with
SQLAlchemy-migrate on a TurboGears application please ?
In fact I want to add a column containing a TSVectorType (
http://sqlalchemy-searchable.readthedocs.org/en/latest/) to 4 of my
existing tables and I’m not sure to know how to proceed…
ex :
search_vector = Column(TSVectorType('name', 'content'))
I watch the given example here
https://sqlalchemy-migrate.readthedocs.org/en/latest/changeset.html with
the col.create() of sqlalchemy-migrate but this example seems to be made
for a « standart » type of column :/
ex :
col = Column('col1', String, default='foobar')col.create(table,
populate_default=True)
So I’m asking here for some advice from you guys…
Thanks a lot for your time.
--
You received this message because you are subscribed to the Google Groups
sqlalchemy group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
[sqlalchemy] sqlalchemy-migrate 0.7.2 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, thanks to the work of a lot of contributors I can announce the new release 0.7.2 of sqlalchemy-migrate today. The release is available at PyPI and our project page [1]. Starting with this release we use readthedocs.org to provide you with online documentation [2]. We want to know about our users. I therefore wrote a mail [3] and hope for your feedback. Release Notes for sqlalchemy-migrate 0.7.2 == Changes since 0.7.1 - --- - - support for SQLAlchemy 0.5.x has been dropped - - Python 2.6 is the minimum supported Python version Documentation * - - add credits for contributors - - add glossary - - improve advice on testing production changes - - improve Sphinx markup - - refine Database Schema Versioning texts, add example for adding/droping columns (#104) - - add more developer related information - - use sphinxcontrib.issuetracker to link to Google Code issue tracker Features - - improved PEP 8 compliance (#122) - - optionally number versions with timestamps instead of sequences (partly pulled from Pete Keen) - - allow descriptions in SQL change script filenames (by Pete Keen) - - improved model generation Fixed Bugs ** - - #83: api test downgrade/upgrade does not work with sql scripts (pulled from Yuen Ho Wong) - - #105: passing a unicode string as the migrate repository fails (add regression test) - - #113: make_update_script_for_model fails with AttributeError: 'SchemaDiff' object has no attribute 'colDiffs' (patch by Jeremy Cantrell) - - #118: upgrade and downgrade functions are reversed when using the command make_update_script_for_model (patch by Jeremy Cantrell) - - #121: manage.py should use the if __name__=='__main__' trick - - #123: column creation in make_update_script_for_model and required API change (by Gabriel de Perthuis) - - #124: compare_model_to_db gets confused by sqlite_sequence (pulled from Dustin J. Mitchell) - - #125: drop column does not work on persistent sqlite databases (pulled from Benoît Allard) - - #128: table rename failure with sqlalchemy 0.7.x (patch by Mark McLoughlin) - - #129: update documentation and help text (pulled from Yuen Ho Wong) Help Wanted === - - Triage bugs on the issue tracker [4] and provide patches as attachments or your own mercurial clones - - Improve documentation, provide useful best practice documents, FAQ and more - - We would like to have some logo artwork (under a free license) idealy as SVG. If you are a skilled graphics artists or know someone who is please feel free to help. Credits === Thanks for all contributors who made the release possible. People contributing patches are mentioned above. A list of contributors can be found at [5]. If you helped us in the past and miss your name there please tell us about your contribution and we will add you to the list. Thanks to all bug reporters and people giving valuable feedback to the migrate-users list and in #sqlalchemy-migrate on IRC. Best Regards, Jan Dittberner [1] http://code.google.com/p/sqlalchemy-migrate/ [2] http://readthedocs.org/docs/sqlalchemy-migrate/en/v0.7.2/ [3] http://groups.google.com/group/migrate-users/msg/f8b3848d6d4ae8d9 [4] http://code.google.com/p/sqlalchemy-migrate/issues/list [5] http://readthedocs.org/docs/sqlalchemy-migrate/en/v0.7.2/credits.html - -- Jan Dittberner - Debian Developer 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.11 (GNU/Linux) iQIcBAEBCAAGBQJOsHtgAAoJEKc+AFVVj7jdPZoQANDaUmu7OemRF3+ARoamEWNN 2J7qbYJQTvZSDTAWtEjvHG2fZr4YuJdtHhmBvJEYBPfZBnAWvQx9/AQ5o7L0FtEZ ADBLRejzvKFR9vnb6ywG5Qs3E/UqLycj6/BsQfzuX9uXS5/j4Vx5GTf4gbsxJIIB l+Ex4xHiEXlN31uf0qBGvI3RpfRLl50v0HCvC7CXxt+pmMnbZcgDkJ6uDVSoogle +ZWjPxTSlHbI8Pm1MB1Nc9O7XdxOh+46A7Dmtv32rRZrybfXX8O9u2gDoQ2/EGvp NGuPtYv6xBW6/immSU1Wco0+WZCAwka+lHNOxblwzhda8vwz8b3+jTkC3XjMG2Cs fM4CBKb/a3udA4Nek5RGSTD1efqiwQzNk8COnYTRVv9xjXh6dejhguY+zPKjPAGf Y9UEtG7Z7q4fhDA/3//As9hiAF3mv5S6CXxjw34MZobm+NkkhDIJf3NWEecvdwy6 l4m/+L9RWotz2um63mXPWROnqRm6c19S78Is1OyUIAqIe09OLLRBEEW22gzoQiB7 atZ4b4Al2NyLUCjIyF270WdNZv3JCW76oJo1wlLs+5iLiC328huRVL289fbdDU6w d0Tdy26bQ7ZxtfXEgoG95miZCBBEYGIFwcLPN+PghIdGLtJtTfBG2yazoqUN2gGz 9oWja8GyuYmC14oaCOrj =1Brd -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
Re: [sqlalchemy] sqlalchemy-migrate 0.7.2 released
congrats on your release ! and on getting all those contributors ! On Nov 1, 2011, at 7:06 PM, Jan Dittberner wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, thanks to the work of a lot of contributors I can announce the new release 0.7.2 of sqlalchemy-migrate today. The release is available at PyPI and our project page [1]. Starting with this release we use readthedocs.org to provide you with online documentation [2]. We want to know about our users. I therefore wrote a mail [3] and hope for your feedback. Release Notes for sqlalchemy-migrate 0.7.2 == Changes since 0.7.1 - --- - - support for SQLAlchemy 0.5.x has been dropped - - Python 2.6 is the minimum supported Python version Documentation * - - add credits for contributors - - add glossary - - improve advice on testing production changes - - improve Sphinx markup - - refine Database Schema Versioning texts, add example for adding/droping columns (#104) - - add more developer related information - - use sphinxcontrib.issuetracker to link to Google Code issue tracker Features - - improved PEP 8 compliance (#122) - - optionally number versions with timestamps instead of sequences (partly pulled from Pete Keen) - - allow descriptions in SQL change script filenames (by Pete Keen) - - improved model generation Fixed Bugs ** - - #83: api test downgrade/upgrade does not work with sql scripts (pulled from Yuen Ho Wong) - - #105: passing a unicode string as the migrate repository fails (add regression test) - - #113: make_update_script_for_model fails with AttributeError: 'SchemaDiff' object has no attribute 'colDiffs' (patch by Jeremy Cantrell) - - #118: upgrade and downgrade functions are reversed when using the command make_update_script_for_model (patch by Jeremy Cantrell) - - #121: manage.py should use the if __name__=='__main__' trick - - #123: column creation in make_update_script_for_model and required API change (by Gabriel de Perthuis) - - #124: compare_model_to_db gets confused by sqlite_sequence (pulled from Dustin J. Mitchell) - - #125: drop column does not work on persistent sqlite databases (pulled from Benoît Allard) - - #128: table rename failure with sqlalchemy 0.7.x (patch by Mark McLoughlin) - - #129: update documentation and help text (pulled from Yuen Ho Wong) Help Wanted === - - Triage bugs on the issue tracker [4] and provide patches as attachments or your own mercurial clones - - Improve documentation, provide useful best practice documents, FAQ and more - - We would like to have some logo artwork (under a free license) idealy as SVG. If you are a skilled graphics artists or know someone who is please feel free to help. Credits === Thanks for all contributors who made the release possible. People contributing patches are mentioned above. A list of contributors can be found at [5]. If you helped us in the past and miss your name there please tell us about your contribution and we will add you to the list. Thanks to all bug reporters and people giving valuable feedback to the migrate-users list and in #sqlalchemy-migrate on IRC. Best Regards, Jan Dittberner [1] http://code.google.com/p/sqlalchemy-migrate/ [2] http://readthedocs.org/docs/sqlalchemy-migrate/en/v0.7.2/ [3] http://groups.google.com/group/migrate-users/msg/f8b3848d6d4ae8d9 [4] http://code.google.com/p/sqlalchemy-migrate/issues/list [5] http://readthedocs.org/docs/sqlalchemy-migrate/en/v0.7.2/credits.html - -- Jan Dittberner - Debian Developer 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.11 (GNU/Linux) iQIcBAEBCAAGBQJOsHtgAAoJEKc+AFVVj7jdPZoQANDaUmu7OemRF3+ARoamEWNN 2J7qbYJQTvZSDTAWtEjvHG2fZr4YuJdtHhmBvJEYBPfZBnAWvQx9/AQ5o7L0FtEZ ADBLRejzvKFR9vnb6ywG5Qs3E/UqLycj6/BsQfzuX9uXS5/j4Vx5GTf4gbsxJIIB l+Ex4xHiEXlN31uf0qBGvI3RpfRLl50v0HCvC7CXxt+pmMnbZcgDkJ6uDVSoogle +ZWjPxTSlHbI8Pm1MB1Nc9O7XdxOh+46A7Dmtv32rRZrybfXX8O9u2gDoQ2/EGvp NGuPtYv6xBW6/immSU1Wco0+WZCAwka+lHNOxblwzhda8vwz8b3+jTkC3XjMG2Cs fM4CBKb/a3udA4Nek5RGSTD1efqiwQzNk8COnYTRVv9xjXh6dejhguY+zPKjPAGf Y9UEtG7Z7q4fhDA/3//As9hiAF3mv5S6CXxjw34MZobm+NkkhDIJf3NWEecvdwy6 l4m/+L9RWotz2um63mXPWROnqRm6c19S78Is1OyUIAqIe09OLLRBEEW22gzoQiB7 atZ4b4Al2NyLUCjIyF270WdNZv3JCW76oJo1wlLs+5iLiC328huRVL289fbdDU6w d0Tdy26bQ7ZxtfXEgoG95miZCBBEYGIFwcLPN+PghIdGLtJtTfBG2yazoqUN2gGz 9oWja8GyuYmC14oaCOrj =1Brd -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at
[sqlalchemy] sqlalchemy-migrate 0.7 released
Hello, today I released sqlalchemy-migrate 0.7. This is the first sqlalchemy-migrate release supporting SQLAlchemy 0.7.0. The only other new functionality is an added migrate.__version__ (requested in issue 111). You can get the new release from our download page [1] or PyPI [2]. The sqlalchemy-migrate maintenance has stalled a bit as some of you might have noticed. We encourage interested developers to join the team and have a look at [3] for a start. Feel free to ask questions on IRC (#sqlalchemy-migrate on Freenode). [1] http://code.google.com/p/sqlalchemy-migrate/downloads/list [2] http://pypi.python.org/pypi/sqlalchemy-migrate [3] http://code.google.com/p/sqlalchemy-migrate/wiki/Development Regards Jan Dittberner -- Jan Dittberner - Debian Developer GPG-key: 4096R/558FB8DD 2009-05-10 B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD http://www.dittberner.info/ signature.asc Description: Digital signature
[sqlalchemy] sqlalchemy-migrate 0.7.1 released
Hello, I just released sqlalchemy-migrate 0.7.1 fixing the behaviour of ChangesetColumn.create() as only functional change. You can get the new release from our download page [1] or PyPI [2]. [1] http://code.google.com/p/sqlalchemy-migrate/downloads/list [2] http://pypi.python.org/pypi/sqlalchemy-migrate Regards Jan Dittberner -- Jan Dittberner - Debian Developer GPG-key: 4096R/558FB8DD 2009-05-10 B2FF 1D95 CE8F 7A22 DF4C F09B A73E 0055 558F B8DD http://www.dittberner.info/ signature.asc Description: Digital signature
[sqlalchemy] sqlalchemy-migrate examples
Hi All, Does anyone have any good examples of migration scripts? The documentation is surprisingly sparse.. Of course, an alernative which doesn't do any abusive monkey patching or have any annoying * imports would be handy. Michael, how's Alembic coming? Chris -- You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
[sqlalchemy] sqlalchemy-migrate 0.6 release
Hello, after more then one year of development the sqlalchemy-migrate development team is proud to announce the release of sqlalchemy-migrate 0.6. This is the first release of sqlalchemy-migrate that supports SQLAlchemy 0.6 and firebird databases. This release introduces a few backward incompatible changes so please consult the changelog [1] to know what might break when upgrading your project. The changelog contains a detailed list of new features, closed bugs and documentation updates too. Thanks go to Michael Bayer for adding SQLAlchemy 0.6 support, Domen Kozar for fixing bugs and greatly improving unit test coverage and Bob Farell for improving the test situation as well. Thanks to Emil Kroymann and Rick Copeland for sending patches. The release is available from PyPI [2] and our project site [3]. A Debian package is available in Debian unstable [4]. The documentation on [5] has been updated too. We hope you enjoy using our new release and would like to get feedback on the migrate-users list [6] and our issue tracker [7]. [1] http://packages.python.org/sqlalchemy-migrate/changelog.html [2] http://pypi.python.org/pypi/sqlalchemy-migrate/0.6 [3] http://code.google.com/p/sqlalchemy-migrate/downloads/list [4] http://packages.debian.org/sid/python-migrate [5] http://packages.python.org/sqlalchemy-migrate/ [6] http://groups.google.com/group/migrate-users [7] http://code.google.com/p/sqlalchemy-migrate/issues/list Regards Jan Dittberner signature.asc Description: Digital signature
[sqlalchemy] SQLAlchemy Migrate
Hi All I'm writing a metadata based schema migration tool. As SQLAlchemy doesn't support much schema modification. I will implement a complete set of schema migration functions one way or another for several of the SQLAlchemy supported databases. My question is, Where should these function reside? Options are : 1) Branch SQLAlchemy and make the modifications 2) Branch SQLAlchemy Migrate and make the modifications 3) Write the code and not distribute it cause no one cares. 4) ? Suggestions ? PS, Thanks Michael Bayer, SQLAlchemy is great. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sqlalchemy group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~--~~~~--~~--~--~---
