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

Heroku Connect Reuse Existing Schema #296

Open
2 tasks done
mdanku opened this issue May 28, 2024 · 1 comment
Open
2 tasks done

Heroku Connect Reuse Existing Schema #296

mdanku opened this issue May 28, 2024 · 1 comment
Labels

Comments

@mdanku
Copy link

mdanku commented May 28, 2024

Required Terms

What service(s) is this request for?

Postgres, Connect

Tell us about what you're trying to solve. What challenges are you facing?

Currently, Heroku Connect requires the dropping or renaming of an existing Postgres schema in order to recreate the Connect instance. This can be a problem if you have views in other schemas that reference tables in the Heroku Connect schema. It would be great if there could be more of an "in-place" approach to recreating Connect instances, where the schema and tables can be reused. Alternatively, it would be helpful if Connect instances did not need to be recreated for cases of a Salesforce sandbox refresh or change to the API version.

@vivekvj01
Copy link

Thank you for bringing this up @mdanku. This seems like a frustrating situation. Let us look into this.

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

No branches or pull requests

2 participants