On Mon, Apr 21, 2014 at 4:37 PM, Tommaso V.
[email protected] wrote:
hi sandip, thanks for the answer, but the problem isn’t using different
tables, but avoid using the same schema_migrations table automatically
generated by rails. I need to use the same database to share most tables,
but different apps have some tables which should be shared so every app has
its migrations, which causes a lot of problems because all the apps use the
If you have to do things in such a chaotic and unorganized way with
multiple apps then get clever and just include all migrations from all
other apps in the other apps and flag them with comments at the top
that state they are there to keep schema_migrations happy, you don’t
need the models at all and rails will detect the tables already exist
and the migrations have already ran and not run them.