Thanks for your reply it was just what I wanted to know! All the best, Mihai
On Nov 6, 3:51 pm, Remi Jolin - SysGroup <[EMAIL PROTECTED]> wrote: > le 06.11.2008 14:46 Remi Jolin - SysGroup a écrit: > > > le 06.11.2008 10:40 Gaetan de Menten a écrit: > > >> On Wed, Nov 5, 2008 at 15:32, Etienne Robillard > >> <[EMAIL PROTECTED]> wrote: > > >>> On November 5, 2008 07:48:10 am Mihai wrote: > > >>>> Hi, > > >>>> I just want to know what is the standard "move" when it comes to > >>>> changing the model and the DB schema according to it. For example I > >>>> want to to change a field from created_on=Field(Date, required=True) > >>>> into created_on=Field(Date). > > >>>> Thanks, > >>>> Mihai > > >>> I'd take a look in $ELIXIR_ROOT/tests/test_versioning.py... :) > > >> Hmm, no this is unrelated. Elixir versioning extension is to keep > >> track of data changes, not schema/metadata changes. > > >> There are several solutions to do what you want. One of them is: > >>http://code.google.com/p/sqlalchemy-migrate/ > > >> There are other projects too, but I can't remember what they are called. > > >>http://code.google.com/p/sqlalchemy-migrate/ > > > There is another project named miruku > > (http://groups.google.com//group//ollix-/miruku) /based on SA-migrate, > > but I don't remember if it handles this specific case (I know you can > > add/delete a "column" and modify some characteristic. It keeps tracks of > > the current model within the DB and can then "automatically" update the > > DB schema based on the model changes > > the correct URL ishttp://groups.google.com/group/ollix-miruku > (cup&paste magic :-( ) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SQLElixir" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlelixir?hl=en -~----------~----~----~----~------~----~------~--~---
