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.
On Wed, Jul 2, 2008 at 6:02 PM, Olli Wang <olliw...@gmail.com> wrote: > 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.
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?
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?
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. :)
On Thu, Jul 3, 2008 at 6:59 PM, Olli Wang <olliw...@gmail.com> wrote:
> 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?
> 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. :)
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% ;)
