On Mon, Apr 21, 2014 at 4:37 PM, Tommaso Visconti <[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 > schema_migrations table
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. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAM5XQnwOKBw5t8at%2BEUPq4qyqcKSz0S7D8hMFnBRZYVU3j4mEg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
