Jason Weathered

I’ve ran into these DNS issues too and I’ve found changing my DNS to use the gateway of the VDE network works well for me. If you want to see...

That’s a real strange one. Does the `active_record_views` table exist in your test database? If so, what does `\d active_record_views` (in `psql`) look like? Are you using `config.active_record.schema_format = :sql`?

I agree that this would be a valuable feature. I am hesitant to add SQL statements to the `.sql` file as to implement this properly would require an SQL syntax...

Having thought about this some more, I think my preferred solution here is a new `after_create_sql` option that you can use in the model file. e.g.: ``` ruby is_view materialized:...

I am against creating a new DSL for indexes but could see supporting running a block in a migration-like context which would give access to `add_index` and any other migration...

This should also probably support rendering partials like Rails does. e.g. `app/models/foo.sql` could render `app/models/foo/_bar.sql` with ``

`` should also up `app/models/abc/_def.sql`. Should work with both `.sql` and `.sql.erb` partials.

It would be nice to trigger reloading if one of the partials is modified. Perhaps the `ActiveRecordViews::RegisteredView` setup could track timestamps for multiple files? A list of partials could be...

It won’t reload automatically in development mode if the timestamp of the `.sql.erb` doesn’t change.

Self note: Make sure there’s docs in the README when full ERB support is added.