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

Database is not included in get_period_boundaries #51

Open
brian-franklin opened this issue Oct 22, 2024 · 0 comments
Open

Database is not included in get_period_boundaries #51

brian-franklin opened this issue Oct 22, 2024 · 0 comments

Comments

@brian-franklin
Copy link

When a database is targeted that is different from the one specified in the profile, the insert_by_period materialization is not taking the database name into account when calling get_period_boundaries.

Additionally, get_period_boundaries is quoting the relation parts and therefore resulting in "object does not exist" error.

  1. get_period_boundaries should have a database argument that is passed from the insert_by_period materialization.
  2. insert_by_period should apply "upper" to the database, schema and identifier or apply "upper" in get_period_boundaries before building the "from" clause where the relation parts are quoted.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant