A new SQLAlchemy migration toolkit - miruku 0.1a3 has been released

[Olli Wang]

Hi, I've just created a new migration toolkit - miruku. The goal of
miruku project is to do the migration work automatically by just one
simple command. There is no need to write upgrade script manually and
there is no version control mechanism. All you have to do is just keep
modifying your model schema code and miruku will do all the upgrading
things for you.

Now you can download and find simple tutorial at http://trac.ollix.org/miruku/

[Shannon -jj Behrens]

How is it possible to not require an upgrade script? What happens if
I'm changing an email field into two fields, one for the username and
one for the server?

-jj

--
It's a walled garden, but the flowers sure are lovely!
http://jjinux.blogspot.com/

[Olli Wang]

On Jul 4, 9:42 am, "Shannon -jj Behrens" <jji...@gmail.com> wrote:
> How is it possible to not require an upgrade script?  What happens if
> I'm changing an email field into two fields, one for the username and
> one for the server?
>
> -jj
>
> --
> It's a walled garden, but the flowers sure are lovely!http://jjinux.blogspot.com/

What miruku does is finding the difference between original schema and
modified schema, then upgrade the original schema to the modified
schema (add/drop columns/tables, etc).
In your question, it seems you just need to add a new email column
which may be located in the same or different table. It doesn't
matter, just change the model schema code by add a new email column
and run miruku upgrade command. Then you will have two email field.
However, currently miruku only support add/drop tables/columns/index.
So there is no way to copy the email value to the new field
automatically. But I think it's a good idea to work it our in the
future. :)

Regards,
Olli

[Shannon -jj Behrens]

I think it's an 80/20 thing. You got 80% of what everyone needs by
writing 20% of the code, and, as usual, I'm obsessed with the
remaining 20% ;)

Happy Hacking!