We accomplish this with custom extensions to the PostgreSQLAdapter, Migration, Migrator and other classes. It is not an ideal solution because we have to patch numerous areas including rspec.rake tasks, database_cleaner rake task and we still dont have a full solution that behaves like you would expect a 'standard' rails app to behave. Furthermore this can create an opaque codebase and confusion for new developers.
Having recently upgraded from Rails2.3.5 to Rails3.0.6 I had to rewrite our rspec tasks and bigfix our Adapter code - but considering the overall complexity of the upgrade, this was a small overhead. In our case, we have a dozen engines often with their own models and migrations. So we have decided that each engine would have its own namespace. So user information would be in the 'identity' namespace for example. I'd love to hear of more support postgresql schemas in rails. Are other databases - is mysql better supported? -- Posted via http://www.ruby-forum.com/. -- 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.
