As far as I know schemas are part of SQL standard and MySQL and SQLite just does not support them (but PostgreSQL does). IMHO, it should not be treated as “database specific” just for that. Schemas may be very useful when you have a lot of tables (e.g. to move dictionaries to another namespace).
среда, 6 мая 2015 г., 10:14:55 UTC+3 пользователь Yves Senn написал: > > I personally don't think we should spend time on expanding the horizon of > `db/schema.rb` for specific database adapters. > Sure, there are already very specific things in there but they generally > lead to issues down the line. With `db/structure.sql` we have a working > solution, maintained by the database vendor. Recently we included a config > option to make it easy to dump > more schemas. > > See https://github.com/rails/rails/pull/19347 > > I'd much rather make `db/structure.sql` a first-class citizen and fix any > issues related to it's usage. > > Cheers, > -- Yves > > On Wednesday, May 6, 2015 at 4:33:16 AM UTC+2, Stenver Jerkku wrote: >> >> What do you guys think of adding support for multiple schemas in the >> schema dump. The way it would work is instead of exporting >> create_table 'table_name' in schema.rb, it would >> create_table 'schema.table_name' >> This could be figured with some configuration flag. >> >> I would be happy to work on this PR myself if you guys think its a good >> idea. If not, please let me know why not. >> > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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]. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
