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.

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

[CT-2865] [Feature] Postgres: Support overwriting tables and views with materialized views #8194

Closed
3 tasks done
damian3031 opened this issue Jul 24, 2023 · 2 comments
Closed
3 tasks done
Labels
enhancement New feature or request

Comments

@damian3031
Copy link
Contributor

Is this your first time submitting a feature request?

  • I have read the expectations for open source contributors
  • I have searched the existing issues, and I could not find an existing issue for this feature
  • I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature

Support overwriting tables and views with materialized views in Postgres adapter.

Describe alternatives you've considered

No response

Who will this benefit?

No response

Are you interested in contributing this feature?

Yes I am

Anything else?

No response

@damian3031 damian3031 added enhancement New feature or request triage labels Jul 24, 2023
@github-actions github-actions bot changed the title [Feature] Postgres: Support overwriting tables and views with materialized views [CT-2865] [Feature] Postgres: Support overwriting tables and views with materialized views Jul 24, 2023
@alison985
Copy link

Does this exist for non-postgres SQL dialects? Why just overwriting tables and views with materialized views?

In general I think dbt needs a way to nicely migrate a table to a view and vice versa. The DROP of the table to make it a view and vice versa currently has no good path/workflow in dbt.

@Fleid
Copy link
Contributor

Fleid commented Jul 28, 2023

Hi @damian3031 - thanks so much for the quick intervention, but we're already planning to enable that in 1.7 ourselves (releasing it early in a beta somewhere in August).

Sadly we can't re-purpose your work, as we are currently refactoring the first internal implementation of MVs that your contribution is based on. We sincerely appreciate your efforts, and hopefully you'll be able to test the new iteration later this summer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants