I have been using schema_format = :sql for adding postgres extensions and haven't had any issues with it.
Anuj On 12 July 2012 07:38, Damien Mathieu <[email protected]> wrote: > In 3.2 and above, you can use schema_format = :sql to generate a > structure.sql file instead of the schema.rb. > > https://github.com/rails/rails/commit/43821bf3513c27913a4d861c83e11b0ad6299916 > > I'm finding using this all the time, as it keeps my views from the > migrations, and it also allows me to activate postgres extensions directly > from the migration. > > Damien MATHIEU | Ingénieur logiciel > 84, rue Chevreul | 69 007 Lyon > Tel. : +33 (0)6 88 42 00 15 | http://dmathieu.com > > > > On 12 July 2012 01:34, Ken Collins <[email protected]> wrote: > >> >> John, >> >> Perhaps make a few directories like db/procedures, db/views, etc and just >> create a rake task in the db namespace that overrides or extends those in >> ActiveRecord's databases.rake? I've had to do this often with legacy >> databases in many forms. This github project talks about it for those >> coming from legacy DBs in SQL Server. >> >> https://github.com/rails-sqlserver/AdventureWorks.Ruby#test-database-tasks >> >> In some cases, I use a little rake extension called #alias_task when >> needing to override a particular task. >> >> >> http://metaskills.net/2010/05/26/the-alias_method_chain-of-rake-override-rake-task/ >> >> In your case, since you want to stick with schema.rb, you could perhaps >> #alias_task on the db:schema:load task, then invoke it, then load up your >> procedures, views etc from the nested db directories? I would be open to >> hearing how others do this too, but I have always found working with >> special schemas and DDL's quite easy with ActiveRecord when you know the >> pressure points. >> >> >> - Ken >> >> >> On Jul 11, 2012, at 6:42 PM, Jon Leighton wrote: >> >> > One thing that I have recently found myself desiring is the ability to >> augment schema.rb with snippets of SQL. >> > >> > For example, I use Postgres, and need to declare some case-insensitive >> indexes. This is not currently possible using Rails directly. >> > >> > I don't want to switch to use the SQL schema dump format, because >> that's highly dependent on the database version. E.g. I am using Postgres >> 9, and another developer is using 8.4. We will probably end up overwriting >> each other's schema.sql files if we went this route. >> > >> > But it would be nice to have, say, a db/schema_extra.sql where we could >> manually place additional stuff like our case-insensitive indexes or >> whatever. >> > >> > Or views... >> > >> > -- >> > http://jonathanleighton.com/ >> > >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups "Ruby on Rails: Core" 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-core?hl=en. >> > >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Ruby on Rails: Core" 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-core?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" 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-core?hl=en. > -- Anuj DUTTA -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en.
