All Versions
16
Latest Version
Avg Release Cycle
127 days
Latest Release
45 days ago

Changelog History
Page 1

  • v1.5.4

    September 16, 2020

    ๐Ÿ›  Fixed

    • โž• Added missing changelog for v1.5.3.
  • v1.5.3

    September 15, 2020

    ๐Ÿ›  Fixed

    • โœจ scenic-oracle_enhanced_adapter has been pulled from rubygems. scenic-oracle_adapter is a current, maintained alternative.
    • โšก๏ธ Updated code snippets - since Rails 5.0, all models inherit from ApplicationRecord (#302)
    • โšก๏ธ Update Caleb's last name

    โž• Added

    • โž• Add Security Policy
  • v1.5.2

    February 06, 2019

    ๐Ÿ›  Fixed

    • The schema statement create_view is now reversible when passed a version argument.
    • Calling refresh_materialized_view with both concurrently and cascade set to true now correctly cascades the concurrent refresh to dependent views.
    • File generation and lookup now operates correctly for schema-qualified names like warehouse.archived_posts.
  • v1.5.1

    February 11, 2019

    ๐Ÿ›  Fixed

    • Passing no_data: true when creating a materialized view would error if the corresponding SQL file had statement-terminating semicolon.
  • v1.5.0

    February 09, 2019

    โž• Added

    • create_view can now be passed materialized: { no_data: true } to create the materialized view without populating it. Generators have been updated to accept a --no-data option.

    ๐Ÿ›  Fixed

    • Passing cascade: true when refreshing a materialized view will no longer error when the view in question has no dependencies.
    • ๐Ÿ›  Fixed runtime deprecation warnings when using pg 0.21 and newer.
    • ๐Ÿ›  Fixed a cascading refresh issue when the name of the view to trigger the refresh is a substring of one of its dependencies.
  • v1.4.1

    December 16, 2017

    ๐Ÿ›  Fixed

    • ๐Ÿš… View migrations created under Rails 5 and newer will use the current migration version in the generated migration class rather than always using 5.0.
  • v1.4.0

    May 19, 2017

    โž• Added

    • refresh_materialized_view now accepts a cascade option, which defaults to false. Setting this option to true will refresh any materialized views the current view depends on first, ensuring the view being refreshed has the most up-to-date information.
    • โšก๏ธ sql_definition argument is now supported when using update_view.

    ๐Ÿ›  Fixed

    • ๐Ÿš… View migrations created under Rails 5 and newer will no longer result in warnings.
    • ar_internal_metadata is no longer included in the schema dump for Rails 5 and newer apps.
    • Using the scenic:model generator will no longer create a fixture or factory.
  • v1.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.
    • Schema-qualify views outside the 'public' namespace, such as scenic.searches

    ๐Ÿ›  Fixed

    • 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.
  • v1.2.0

    February 06, 2016

    โž• Added

    • ๐Ÿš… The generators now accept namespaced view definitions. For example: rails 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.
    • โšก๏ธ Calling update_view for a materialized view now properly finds associated
      indexes for automatic reapplication. An issue in the previous index query was
      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
    master.

    Full Changelog

  • v1.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
      all operations.

    Full Changelog