Re: [Fez-developers] incremental upgrades

[Matthew S. <yo....@gm...>]

what does your fez_config table look like?  I like what you have done
there so how about we merge it.

We need to get the git -> svn conversion going!

Matt


On 1/17/07, Jun Yamog <ju...@ca...> wrote:
> Hi Matt,
>
> Yes this is pretty good.  I have used ROR migration and liked it.  For
> our Fez we just actually copied your /upgrade/index.php and allowed it
> to do "up" only upgrade script.
>
> Similar to ROR and other framework.  We do a look up on the db, then
> check which sql files needs to run.  The upgrade script uses
> upgradeYYYYMMDDXX.sql convention.
>
> Here is your modified upgrade script:
>
> http://git.catalyst.net.nz/gitweb?p=fezr2.git;a=blob;h=32d48580f3ba80994cb28d33a3e7f4e87badff54;hb=oarinz-1.3;f=upgrade/local/index.php
>
> I am in favor of using ROR like upgrade scripts.  But we are not picky,
> as long as it works even for only "up" direction.  Looking forward to
> getting a incremental upgrade in Fez, as this will greatly help us in
> keeping track of Fez and keep our code as close as possible.  Thanks.
>
> Jun
>
> Matthew Smith wrote:
> > Hi All,
> >
> > I'm thinking about having a system for incremental upgrades based on
> > the migrations concept in ruby on rails.  How it works is that each
> > time you modify the database schema, you save the SQL command used to
> > make the change to a file that is numbered.  e.g.
> >
> > 001_add_max_downloads_column.php
> > 002_drop_statistics_table.php
> >
> > Each file is called a migration.
> >
> > Inside each migration is a migration subclass which overrides two
> > methods 'up' and 'down'.  The 'up' method runs the SQL queries to make
> > the change to the database, the 'down' method reverses the change in
> > case you want to roll back (though i'm not sure we'll use this).
> >
> > The database will also have to keep a version number somewhere so that
> > we know which migrations have been applied.  For example, if the
> > database is at version 13 and we unpack a new fez version, the upgrade
> > script knows that it needs to get to version 15 so it applies
> > migrations 14 and 15.
> >
> > The main thing is that we'll have to remember to make all of our
> > changes to the database into  migration scripts.
> >
> > get it?
> >
> > Matt
> >
> > -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share your
> > opinions on IT & business topics through brief surveys - and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Fez-developers mailing list
> > Fez...@li...
> > https://lists.sourceforge.net/lists/listinfo/fez-developers
> >
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Fez-developers mailing list
> Fez...@li...
> https://lists.sourceforge.net/lists/listinfo/fez-developers
>