Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: use correct schema for MV target tables #244

Merged
merged 2 commits into from
Feb 2, 2024
Merged

fix: use correct schema for MV target tables #244

merged 2 commits into from
Feb 2, 2024

Commits on Jan 25, 2024

  1. fix: use correct schema when updating MVs 

    The existing implementation passes just the name for `target_table`,
which ultimately means that the target schema is not included when the
final SQL is generated. By passing the entire relation object, the
correct target schema will be present in the final SQL.
    @SoryRawyer
    SoryRawyer committed Jan 25, 2024
    Configuration menu
    Copy the full SHA
    d55f4d4 View commit details
    Browse the repository at this point in the history

  2. update MV tests 

    Provide a custom schema to make sure that the full target table
name (schema + relation name) is included in the CREATE MATERIALIZED
VIEW statement
    @SoryRawyer
    SoryRawyer committed Jan 25, 2024
    Configuration menu
    Copy the full SHA
    f449300 View commit details
    Browse the repository at this point in the history