You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: