scenic 1.7.0 → 1.9.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b378292bd7d642dcd235d01f5a31d94c74065b798ab469a9c091f68e936f4d9c
-  data.tar.gz: b97f6e156685d4c03761543d5748f1381447c94cfcc42f7d6ddb8714e16791d0
+  metadata.gz: 772babaa9c177e3f24e45e0b61c7bed0475b5267806bea563d4a7ec1e97830c9
+  data.tar.gz: af0d81ab175baa0b0ac35d11216f76bb9d1663f3483fde733a862cff92067a01
 SHA512:
-  metadata.gz: 4ffb0c73e52da5122a8ce3092b7f280d1a1dcaac9ca03a5f8ea63fe361d1b011d3c71f54706ff17d8ee1768fbdc1ba32c38bfebbcda320271e0b751eaea340f3
-  data.tar.gz: 846d53ffe8c0d0209ab6517c47e0447ee3b40a81e5f55f845f16a1b3f697cebd44ad38550a5fe8d10016ab19b3c1197f36ea9f3f5f7f42395a1431790684e0c1
+  metadata.gz: ac9d6aa1abb1bea6d69d50de6aad86e0a567abd2b1631645b2f62d1bbd687b362e5af7ebe6fde7ad94fc6203a76df57fb3893a4f677b0def61740bc7af1f92a5
+  data.tar.gz: 59b77cb6f2b51334a3cefb6ef121a25354c7d202bef2c9898202da84d4a6b889898cc6d6b5bcd7e38b37b020501cff80628c843467d6d3a03dee6f309fb0a860

data/.github/workflows/ci.yml

@@ -7,15 +7,40 @@ on:
     branches: "*"
 
 jobs:
+  standard:
+    name: Lint with Standard
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Run standardrb
+        uses: standardrb/standard-ruby-action@f533e61f461ccb766b2d9c235abf59be02aea793
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+    permissions:
+      checks: write
+      contents: read
+
   build:
     name: Ruby ${{ matrix.ruby }}, Rails ${{ matrix.rails }}
+    continue-on-error: ${{ matrix.continue-on-error }}
 
     strategy:
       fail-fast: false
       matrix:
-        ruby: ["2.7", "3.0", "3.1"]
-        rails: ["6.1", "7.0"]
+        ruby: ["3.4", "3.3"]
+        rails: ["8.0", "7.2"]
         continue-on-error: [false]
+        include:
+          - ruby: "3.4"
+            rails: "main"
+            continue-on-error: true
+          - ruby: "head"
+            rails: "main"
+            continue-on-error: true
 
     runs-on: ubuntu-latest
 
@@ -40,7 +65,7 @@ jobs:
 
     steps:
       - name: Checkout
-        uses: actions/checkout@v2
+        uses: actions/checkout@v4
 
       - name: Install Ruby ${{ matrix.ruby }}
         uses: ruby/setup-ruby@v1
@@ -54,7 +79,7 @@ jobs:
         run: bundle lock
 
       - name: Cache dependencies
-        uses: actions/cache@v1
+        uses: actions/cache@v4
         with:
           path: vendor/bundle
           key: bundle-${{ hashFiles('Gemfile.lock') }}

data/.gitignore

@@ -18,3 +18,4 @@ tmp
 gemfiles/*.lock
 .DS_Store
 .ruby-version
+.vscode/

data/CHANGELOG.md

@@ -5,19 +5,44 @@ changelog, see the [commits] for each version via the version links.
 
 [commits]: https://github.com/scenic-views/scenic/commits/master
 
+## [1.9.0] - June 30, 2025
+
+[1.9.0]: https://github.com/scenic-views/scenic/compare/v1.8.0...v1.9.0
+
+### Added
+
+- Added topological sorting of views when dumping schema. This should limit
+  unrelated changes to schema.rb once the views are sorted the first time.
+- Added `side_by_side` mode to materialized view updates. This creates the
+  updated materialized view with a temporary name before swapping it with the
+  live view, minimizing the time the view is locked for updating.
+
+### Fixed
+
+- Only refresh concurrently if the materialized view is populated.
+
+## [1.8.0] - March 28, 2024
+
+[1.8.0]: https://github.com/scenic-views/scenic/compare/v1.7.0...v1.8.0
+
+### Added
+
+- Added `#populated?` to check the state of materialized views - _Daisuke
+  Fujimura_, _Dr Nic Williams_
+
 ## [1.7.0] - December 8, 2022
 
 [1.7.0]: https://github.com/scenic-views/scenic/compare/v1.6.0...v1.7.0
 
 ### Added
 
-* Added the `--replace` CLI flag to generate a migration that uses the
-  `replace_view` schema statement - *Dan Hixon*
+- Added the `--replace` CLI flag to generate a migration that uses the
+  `replace_view` schema statement - _Dan Hixon_
 
 ### Fixed
 
-* Fixed deprecation notice from newer versions of ERB when using scenic
-  generators - *Ali Ismayilov*
+- Fixed deprecation notice from newer versions of ERB when using scenic
+  generators - _Ali Ismayilov_
 
 ## [1.6.0] - February 13, 2022
 
@@ -25,9 +50,9 @@ changelog, see the [commits] for each version via the version links.
 
 ### Fixed
 
-* Exclude pg_stat_statements_info (#349) 76bface - *Caleb Hearth*
-* Fix serialization of views with backslashes c625d1b - *Ben Sheldon*
-* Handle ActiveRecord table name prefix and suffix b1544dc - *Derek Prior*
+- Exclude pg*stat_statements_info (#349) 76bface - \_Caleb Hearth*
+- Fix serialization of views with backslashes c625d1b - _Ben Sheldon_
+- Handle ActiveRecord table name prefix and suffix b1544dc - _Derek Prior_
 
 ## [1.5.5] - December 15, 2021
 
@@ -100,7 +125,6 @@ changelog, see the [commits] for each version via the version links.
 - Fixed a cascading refresh issue when the name of the view to trigger the
   refresh is a substring of one of its dependencies.
 
-
 [1.5.0]: https://github.com/scenic-views/scenic/compare/v1.4.1...v1.5.0
 
 ## [1.4.1] - December 15, 2017
@@ -135,26 +159,30 @@ changelog, see the [commits] for each version via the version links.
 ## [1.3.0] - May 27, 2016
 
 ### Added
+
 - Add `replace_view` migration statement, which issues `CREATE OR REPLACE
-  VIEW` rather than `CREATE VIEW` or `DROP VIEW` and `CREATE VIEW`.
+VIEW` rather than `CREATE VIEW` or `DROP VIEW` and `CREATE VIEW`.
 - Schema-qualify views outside the 'public' namespace, such as
   `scenic.searches`
 
 ### Fixed
-* Singularize generated model name when injecting into class.
+
+- Singularize generated model name when injecting into class.
   Previously, pluralized names would issue a warning and Scenic would
   attempt to insert model code into the pluralized model file.
-* Convert shell-based smoke tests to RSpec syntax.
+- Convert shell-based smoke tests to RSpec syntax.
 
 [1.3.0]: https://github.com/scenic-views/scenic/compare/v1.2.0...v1.3.0
 
 ## [1.2.0] - February 5, 2016
 
 ### Added
+
 - The generators now accept namespaced view definitions. For example: `rails
-  generate scenic:view my_app.users`.
+generate scenic:view my_app.users`.
 
 ### Fixed
+
 - Materialized view indexes are now properly dumped to `db/schema.rb`. This was
   an oversight in previous releases, meaning `rake db:schema:load` was missing
   indexes.
@@ -163,7 +191,7 @@ changelog, see the [commits] for each version via the version links.
   returning no indexes.
 
 **Note**: Dumping materialized view indexes will produce an invalid
-`db/schema.rb` file  under Rails 5 beta 1 and beta 2. This is fixed on Rails
+`db/schema.rb` file under Rails 5 beta 1 and beta 2. This is fixed on Rails
 master.
 
 [1.2.0]: https://github.com/scenic-views/scenic/compare/v1.1.1...v1.2.0
@@ -171,8 +199,9 @@ master.
 ## [1.1.1] - January 29, 2016
 
 ### Fixed
+
 - Some schema operations were failing with a `PG::ConnectionBad: connection is
-  closed` error. This has been fixed by ensuring we grab a fresh connection for
+closed` error. This has been fixed by ensuring we grab a fresh connection for
   all operations.
 
 [1.1.1]: https://github.com/scenic-views/scenic/compare/v1.1.0...v1.1.1
@@ -180,12 +209,14 @@ master.
 ## [1.1.0] - January 8, 2016
 
 ### Added
+
 - Added support for updating materialized view definitions while maintaining
   existing indexes that are still applicable after the update.
 - Added support for refreshing materialized views concurrently (requires
   Postgres 9.4 or newer).
 
 ### Fixed
+
 - The schema dumper will now dump views and materialized views together in the
   order they are returned by Postgres. This fixes issues when loading views that
   depend on other views via `rake db:schema:load`.
@@ -200,26 +231,30 @@ master.
 ## [1.0.0] - November 23, 2015
 
 ### Added
+
 - Added support for [materialized views].
 - Allow changing the database adapter via `Scenic::Configuration`.
 
 ### Fixed
+
 - Improved formatting of the view when dumped to `schema.rb`.
 - Fixed generation of namespaced models by using ActiveRecord's own model
   generator.
 - Eliminated `alias_method_chain` deprecation when running with Rails master
   (5.0).
 
-[materialized views]:https://github.com/scenic-views/scenic/blob/v1.0.0/README.md
+[materialized views]: https://github.com/scenic-views/scenic/blob/v1.0.0/README.md
 [1.0.0]: https://github.com/scenic-views/scenic/compare/v0.3.0...v1.0.0
 
 ## [0.3.0] - January 23, 2015
 
 ### Added
+
 - Previous view definition is copied into new view definition file when updating
   an existing view.
 
 ### Fixed
+
 - We avoid dumping views that belong to Postgres extensions.
 - `db/schema.rb` is prettier thanks to a blank line after each view definition.
 
@@ -228,6 +263,7 @@ master.
 ## [0.2.1] - January 5, 2015
 
 ### Fixed
+
 - View generator will now create `db/views` directory if necessary.
 
 [0.2.1]: https://github.com/scenic-views/scenic/compare/v0.2.0...v0.2.1
@@ -235,9 +271,11 @@ master.
 ## [0.2.0] - August 11, 2014
 
 ### Added
+
 - Teach view generator to update existing views.
 
 ### Fixed
+
 - Raise an error if view definition is empty.
 
 [0.2.0]: https://github.com/scenic-views/scenic/compare/v0.1.0...v0.2.0
@@ -247,8 +285,8 @@ master.
 Scenic makes it easier to work with Postgres views in Rails.
 
 It introduces view methods to ActiveRecord::Migration and allows views to be
-dumped to db/schema.rb.  It provides generators for models, view definitions,
-and migrations.  It is built around a basic versioning system for view
+dumped to db/schema.rb. It provides generators for models, view definitions,
+and migrations. It is built around a basic versioning system for view
 definition files.
 
 In short, go add a view to your app.

data/CONTRIBUTING.md

@@ -13,6 +13,7 @@ agree to abide by our [code of conduct].
 3. Run `rake` to verify that the tests pass against the version of Rails you are
    running locally.
 4. Make your change with new passing tests, following existing style.
+5. Run `standardrb --fix` to ensure your code is formatted correctly.
 5. Write a [good commit message], push your fork, and submit a pull request.
 6. CI will run the test suite on all configured versions of Ruby and Rails.
    Address any failures.

data/FUNDING.yml

@@ -0,0 +1 @@
+github: [calebhearth, derekprior]

data/Gemfile

@@ -3,12 +3,12 @@ source "https://rubygems.org"
 # Specify your gem's dependencies in scenic.gemspec
 gemspec
 
-rails_version = ENV.fetch("RAILS_VERSION", "6.1")
+rails_version = ENV.fetch("RAILS_VERSION", "8.0")
 
-if rails_version == "master"
-  rails_constraint = { github: "rails/rails" }
+rails_constraint = if rails_version == "main"
+  {github: "rails/rails"}
 else
-  rails_constraint = "~> #{rails_version}.0"
+  "~> #{rails_version}.0"
 end
 
 gem "rails", rails_constraint

data/README.md

@@ -4,7 +4,6 @@
 
 [![Build Status](https://github.com/scenic-views/scenic/actions/workflows/ci.yml/badge.svg)](https://github.com/scenic-views/scenic/actions/workflows/ci.yml)
 [![Documentation Quality](http://inch-ci.org/github/scenic-views/scenic.svg?branch=master)](http://inch-ci.org/github/scenic-views/scenic)
-[![Reviewed by Hound](https://img.shields.io/badge/Reviewed_by-Hound-8E64B0.svg)](https://houndci.com)
 
 Scenic adds methods to `ActiveRecord::Migration` to create and manage database
 views in Rails.
@@ -25,7 +24,7 @@ Scenic ships with support for PostgreSQL. The adapter is configurable (see
 
 If you're using Postgres, Add `gem "scenic"` to your Gemfile and run `bundle
 install`. If you're using something other than Postgres, check out the available
-[third party adapters](https://github.com/scenic-views/scenic#faqs).
+[third-party adapters](https://github.com/scenic-views/scenic#when-will-you-support-mysql-sqlite-or-other-databases).
 
 ## Great, how do I create a view?
 
@@ -86,14 +85,17 @@ schema in the new definition and run the `update_view` migration.
 
 ## What if I want to change a view without dropping it?
 
-The `update_view` statement used by default will drop your view then create
-a new version of it.
+The `update_view` statement used by default will drop your view then create a
+new version of it. This may not be desirable when you have complicated
+hierarchies of dependent views.
 
-This is not desirable when you have complicated hierarchies of views, especially
-when some of those views may be materialized and take a long time to recreate.
+Scenic offers a `replace_view` schema statement, resulting in a `CREATE OR
+REPLACE VIEW` SQL query which will update the supplied view in place, retaining
+all dependencies. Materialized views cannot be replaced in this fashion, though
+the `side_by_side` update strategy may yield similar results (see below).
 
-You can use `replace_view` to generate a CREATE OR REPLACE VIEW SQL statement
-instead by adding the `--replace` option to the generate command:
+You can generate a migration that uses the `replace_view` schema statement by
+passing the `--replace` option to the `scenic:view` generator:
 
 ```sh
 $ rails generate scenic:view search_results --replace
@@ -101,9 +103,6 @@ $ rails generate scenic:view search_results --replace
       create  db/migrate/[TIMESTAMP]_update_search_results_to_version_2.rb
 ```
 
-See Postgres documentation on how this works:
-http://www.postgresql.org/docs/current/static/sql-createview.html
-
 The migration will look something like this:
 
 ```ruby
@@ -114,8 +113,6 @@ class UpdateSearchResultsToVersion2 < ActiveRecord::Migration
 end
 ```
 
-You can run the migration and the view will be replaced instead.
-
 ## Can I use this view to back a model?
 
 You bet! Using view-backed models can help promote concepts hidden in your
@@ -127,6 +124,11 @@ no different than a table.
 class SearchResult < ApplicationRecord
   belongs_to :searchable, polymorphic: true
 
+  # If you want to be able to call +Model.find+, you
+  # must declare the primary key. It can not be
+  # inferred from column information.
+  # self.primary_key = :id
+
   # this isn't strictly necessary, but it will prevent
   # rails from calling save, which would fail anyway.
   def readonly?
@@ -136,7 +138,7 @@ end
 ```
 
 Scenic even provides a `scenic:model` generator that is a superset of
-`scenic:view`.  It will act identically to the Rails `model` generator except
+`scenic:view`. It will act identically to the Rails `model` generator except
 that it will create a Scenic view migration rather than a table migration.
 
 There is no special base class or mixin needed. If desired, any code the model
@@ -184,6 +186,44 @@ you would need to refresh view B first, then right after refresh view A. If you
 would like this cascading refresh of materialized views, set `cascade: true`
 when you refresh your materialized view.
 
+## Can I update the definition of a materialized view without dropping it?
+
+No, but Scenic can help you approximate this behavior with its `side_by_side`
+update strategy.
+
+Generally, changing the definition of a materialized view requires dropping it
+and recreating it, either without data or with a non-concurrent refresh. The
+materialized view will be locked for selects during the refresh process, which
+can cause problems in your application if the refresh is not fast.
+
+The `side_by_side` update strategy prepares the new version of the view under a
+temporary name. This includes copying the indexes from the original view and
+refreshing the data. Once prepared, the original view is dropped and the new
+view is renamed to the original view's name. This process minimizes the time the
+view is locked for selects at the cost of additional disk space.
+
+You can generate a migration that uses the `side_by_side` strategy by passing
+the `--side-by-side` option to the `scenic:view` generator:
+
+```sh
+$ rails generate scenic:view search_results --materialized --side-by-side
+      create  db/views/search_results_v02.sql
+      create  db/migrate/[TIMESTAMP]_update_search_results_to_version_2.rb
+```
+
+The migration will look something like this:
+
+```ruby
+class UpdateSearchResultsToVersion2 < ActiveRecord::Migration
+  def change
+    update_view :search_results,
+      version: 2,
+      revert_to_version: 1,
+      materialized: { side_by_side: true }
+  end
+end
+```
+
 ## I don't need this view anymore. Make it go away.
 
 Scenic gives you `drop_view` too:
@@ -197,7 +237,7 @@ end
 
 ## FAQs
 
-**Why do I get an error when querying a view-backed model with `find`, `last`, or `first`?**
+### Why do I get an error when querying a view-backed model with `find`, `last`, or `first`?
 
 ActiveRecord's `find` method expects to query based on your model's primary key,
 but views do not have primary keys. Additionally, the `first` and `last` methods
@@ -212,7 +252,7 @@ class People < ApplicationRecord
 end
 ```
 
-**Why is my view missing columns from the underlying table?**
+### Why is my view missing columns from the underlying table?
 
 Did you create the view with `SELECT [table_name].*`? Most (possibly all)
 relational databases freeze the view definition at the time of creation. New
@@ -225,7 +265,7 @@ add_column :posts, :title, :string
 update_view :posts_with_aggregate_data, version: 2, revert_to_version: 2
 ```
 
-**When will you support MySQL, SQLite, or other databases?**
+### When will you support MySQL, SQLite, or other databases?
 
 We have no plans to add first-party adapters for other relational databases at
 this time because we (the maintainers) do not currently have a use for them.
@@ -233,7 +273,7 @@ It's our experience that maintaining a library effectively requires regular use
 of its features. We're not in a good position to support MySQL, SQLite or other
 database users.
 
-Scenic *does* support configuring different database adapters and should be
+Scenic _does_ support configuring different database adapters and should be
 extendable with adapter libraries. If you implement such an adapter, we're happy
 to review and link to it. We're also happy to make changes that would better
 accommodate adapter gems.
@@ -241,20 +281,39 @@ accommodate adapter gems.
 We are aware of the following existing adapter libraries for Scenic which may
 meet your needs:
 
-* [`scenic_sqlite_adapter`](<https://github.com/pdebelak/scenic_sqlite_adapter>)
-* [`scenic-mysql_adapter`](<https://github.com/EmpaticoOrg/scenic-mysql_adapter>)
-* [`scenic-sqlserver-adapter`](<https://github.com/ClickMechanic/scenic_sqlserver_adapter>)
-* [`scenic-oracle_adapter`](<https://github.com/cdinger/scenic-oracle_adapter>)
+- [`scenic_sqlite_adapter`](https://github.com/pdebelak/scenic_sqlite_adapter)
+- [`scenic-mysql_adapter`](https://github.com/cainlevy/scenic-mysql_adapter)
+- [`scenic-sqlserver-adapter`](https://github.com/ClickMechanic/scenic_sqlserver_adapter)
+- [`scenic-oracle_adapter`](https://github.com/cdinger/scenic-oracle_adapter)
 
 Please note that the maintainers of Scenic make no assertions about the
 quality or security of the above adapters.
 
 ## About
 
+### Used By
+
 Scenic is used by some popular open source Rails apps:
-[Mastodon](<https://github.com/mastodon/mastodon/>),
-[Code.org](<https://github.com/code-dot-org/code-dot-org>), and
-[Lobste.rs](<https://github.com/lobsters/lobsters/>).
+[Mastodon](https://github.com/mastodon/mastodon/),
+[Code.org](https://github.com/code-dot-org/code-dot-org), and
+[Lobste.rs](https://github.com/lobsters/lobsters/).
+
+### Related projects
+
+- [`fx`](https://github.com/teoljungberg/fx) Versioned database functions and
+  triggers for Rails
+
+### Media
+
+Here are a few posts we've seen discussing Scenic:
+
+- [Announcing Scenic - Versioned Database Views for Rails](https://thoughtbot.com/blog/announcing-scenic--versioned-database-views-for-rails) by Derek Prior for thoughtbot
+- [Effectively Using Materialized Views in Ruby on Rails](https://pganalyze.com/blog/materialized-views-ruby-rails) by Leigh Halliday for pganalyze
+- [Optimizing String Concatenation in Ruby on Rails](https://dev.to/pimp_my_ruby/from-slow-to-lightning-fast-optimizing-string-concatenation-in-ruby-on-rails-28nk)
+- [Materialized Views In Ruby On Rails With Scenic](https://www.ideamotive.co/blog/materialized-views-ruby-rails-scenic) by Dawid Karczewski for Ideamotive
+- [Using Scenic and SQL views to aggregate data](https://dev.to/weareredlight/using-scenic-and-sql-views-to-aggregate-data-226k) by André Perdigão for Redlight Software
+
+### Maintainers
 
 Scenic is maintained by [Derek Prior], [Caleb Hearth], and you, our
 contributors.

data/Rakefile

@@ -26,4 +26,4 @@ RSpec::Core::RakeTask.new("spec:acceptance") do |task|
 end
 
 desc "Run the specs and acceptance tests"
-task default: %w(spec spec:acceptance)
+task default: %w[spec spec:acceptance]

data/bin/standardrb

@@ -0,0 +1,27 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+#
+# This file was generated by Bundler.
+#
+# The application 'standardrb' is installed as part of a gem, and
+# this file is here to facilitate running it.
+#
+
+ENV["BUNDLE_GEMFILE"] ||= File.expand_path("../Gemfile", __dir__)
+
+bundle_binstub = File.expand_path("bundle", __dir__)
+
+if File.file?(bundle_binstub)
+  if File.read(bundle_binstub, 300).include?("This file was generated by Bundler")
+    load(bundle_binstub)
+  else
+    abort("Your `bin/bundle` was not generated by Bundler, so this binstub cannot run.
+Replace `bin/bundle` by running `bundle binstubs bundler --force`, then run this command again.")
+  end
+end
+
+require "rubygems"
+require "bundler/setup"
+
+load Gem.bin_path("standard", "standardrb")

data/lib/generators/scenic/materializable.rb

@@ -14,7 +14,14 @@ module Scenic
           type: :boolean,
           required: false,
           desc: "Adds WITH NO DATA when materialized view creates/updates",
-          default: false
+          default: false,
+          aliases: ["--no-data"]
+        class_option :side_by_side,
+          type: :boolean,
+          required: false,
+          desc: "Uses side-by-side strategy to update materialized view",
+          default: false,
+          aliases: ["--side-by-side"]
         class_option :replace,
           type: :boolean,
           required: false,
@@ -35,6 +42,25 @@ module Scenic
       def no_data?
         options[:no_data]
       end
+
+      def side_by_side?
+        options[:side_by_side]
+      end
+
+      def materialized_view_update_options
+        set_options = {no_data: no_data?, side_by_side: side_by_side?}
+          .select { |_, v| v }
+
+        if set_options.empty?
+          "true"
+        else
+          string_options = set_options.reduce("") do |memo, (key, value)|
+            memo + "#{key}: #{value}, "
+          end
+
+          "{ #{string_options.chomp(", ")} }"
+        end
+      end
     end
   end
 end

data/lib/generators/scenic/model/model_generator.rb

@@ -15,7 +15,7 @@ module Scenic
           [file_path.singularize],
           options.merge(
             fixture_replacement: false,
-            migration: false,
+            migration: false
           )
       end
 
@@ -34,23 +34,14 @@ module Scenic
       private
 
       def evaluate_template(source)
-        source  = File.expand_path(find_in_source_paths(source.to_s))
+        source = File.expand_path(find_in_source_paths(source.to_s))
         context = instance_eval("binding", __FILE__, __LINE__)
 
-        if ERB.instance_method(:initialize).parameters.assoc(:key) # Ruby 2.6+
-          erb = ERB.new(
-            ::File.binread(source),
-            trim_mode: "-",
-            eoutvar: "@output_buffer",
-          )
-        else
-          erb = ERB.new(
-            ::File.binread(source),
-            nil,
-            "-",
-            "@output_buffer",
-          )
-        end
+        erb = ERB.new(
+          ::File.binread(source),
+          trim_mode: "-",
+          eoutvar: "@output_buffer"
+        )
 
         erb.result(context)
       end

data/lib/generators/scenic/model/templates/model.erb

@@ -1,3 +1,7 @@
   def self.refresh
     Scenic.database.refresh_materialized_view(table_name, concurrently: false, cascade: false)
   end
+
+  def self.populated?
+    Scenic.database.populated?(table_name)
+  end

data/lib/generators/scenic/view/templates/db/migrate/update_view.erb

@@ -1,11 +1,11 @@
 class <%= migration_class_name %> < <%= activerecord_migration_class %>
   def change
-  <% method_name = replace_view? ? 'replace_view' : 'update_view' %>
+  <%- method_name = replace_view? ? 'replace_view' : 'update_view' -%>
   <%- if materialized? -%>
     <%= method_name %> <%= formatted_plural_name %>,
       version: <%= version %>,
       revert_to_version: <%= previous_version %>,
-      materialized: <%= no_data? ? "{ no_data: true }" : true %>
+      materialized: <%= materialized_view_update_options %>
   <%- else -%>
     <%= method_name %> <%= formatted_plural_name %>, version: <%= version %>, revert_to_version: <%= previous_version %>
   <%- end -%>