Patching the schema dump to ignore the engine_schema_info table was on my hitlist too, but a patch would be more than welcome, so please do look into that if you can.
W.r.t. just modifying the existing schema_info table, I considered that but came to the conclusion that it would be the worse of two evils; adding version information about individual engines would, as you say, involve adding new columns each time a new engine is encountered, which then means that the migration system has to ALTER tables rather than just adding rows. It also puts the engine schema information at the mercy of whatever processes are playing with the schema info table, which could concievably be a bad thing. Perhaps I'm being overprotective here though... I do try and keep an open mind though - if you wanted to work up a patch for that too, it would definitely be worthy of discussion. - james On 3/8/06, Jeff Lindsay <[EMAIL PROTECTED]> wrote: > When using 'rake db_schema_dump' Rails will ignore its own schema > version table, so I'm trying to extend it to ignore engines' as well. > It's a bit tough though because of the way Rails loads the > SchemaDumper class... I'm still playing with it. > > Anyway, if I get it working, shall I supply a patch? > > Sidenote: I hate Rails making a table for schema info... so I'm doubly > pained to see engines add another for the same reason. I was thinking > it would be nice of engines just extended the Rails table... I don't > think Rails cares of there's extra columns and as long as the app > migration version is the first record, it should keep working. > Thoughts? > > -- > Jeff Lindsay > http://blogrium.com/ > _______________________________________________ > engine-developers mailing list > [email protected] > http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org > -- * J * ~ _______________________________________________ engine-developers mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
