I just realized extended the rails version table would solve the original issue... which is nice because it looks like it might be impossible to properly extend the SchemaDumper class from a plugin or the environment the way the rake task loads it.
I'm a rake noob, can we overwrite rake tasks? 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/ > -- Jeff Lindsay http://blogrium.com/ _______________________________________________ engine-developers mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-developers-rails-engines.org
