I'd like to at least see support for SQL view migrations in rails, especially since ActiveRecord already supports read only models for SQL views fairly well. I feel that scenic personally does a fairly good job, and I'd understand if the majority of rails maintainers don't want to add to the rails maintenance burden for SQL view migration support. What would wrapping the entire migrations sequence be used for? Better ways to wrap and augment schema generation could be improved IMO. Thoughts?
On Saturday, March 9, 2019 at 7:14:51 AM UTC-8, Jason Kenney wrote: > > One issue I stumble on often is Postgres sql dependencies for advanced > structure and rails migrations. > > Scenic is helpful if its just views, but.... I actually think its approach > can get in the way after you have something_vw_56.sql... > > What would be REALLY helpful is if rails had built-in-hooks to just > specify sql code that can run either: > - before the migration sequence > - after the migration sequence > - before a schema load (but after database creation) > - after schema load > - around a migration that has a particular tag associated with it (so you > can drop specific materialized views, indexes, and recreate them only for a > particular migration, and not on every single migration). > > > -- 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 rubyonrails-core+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-core/8ed25528-52e9-462d-963a-e85f752e22d4%40googlegroups.com.
