merb_datamapper has a rake task to generate the sequential migrations, I would stick to this convention personally.
-Matt On Wed, Nov 26, 2008 at 11:30 AM, Justin Reagor <[EMAIL PROTECTED]> wrote: > On Nov 26, 2008, at 10:59 AM, Martin Frost wrote: > > The definition of these tables are written as properties in the definitions > of the User and Article model. > Since the default ORM in Merb is DataMapper, when you run rake > db:automigrate, rake will check through your models (in app/models/) and > create tables based on which properties exist in your model classes. > > This is actually mentioned in the "Generate your first app" article on the > wiki. Quote: > > "Because DataMapper models define the schema mapping, DataMapper can > figure out what your database should look like." > > > That reminds me of a question I had, where do DM migrations typically go > within the directory structure of a Merb application? I understand I can put > them where ever I want, but traditionally does anyone have a preference they > use, or just follow db/migrate from the past? > > :: cheapRoc > :: [EMAIL PROTECTED] > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
