Hi,
poking round the source I see:
def schema_migrations_table_name
Base.table_name_prefix + 'schema_migrations' +
Base.table_name_suffix
end
in activerecord-2.1.0/lib/active_record/migration.rb
I suppose you could override this method in that class and then call
initialize_schema_migrations_table.
Have you tried just having multiple migrations and just letting the
migration code work it out for itself? Rails should handle
intermediate migrations with timestamps (I think!)
Allan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" 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/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
