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

fix: prevent deletion of 'raster_columns' and 'raster_overviews' PostGIS columns in prisma migrate #3198

Merged
merged 3 commits into from Sep 17, 2022

Conversation

jkomyno
Copy link
Contributor

@jkomyno jkomyno commented Sep 16, 2022

@jkomyno jkomyno requested a review from a team as a code owner September 16, 2022 12:32
@jkomyno jkomyno added this to the 4.4.0 milestone Sep 16, 2022
@jkomyno
Copy link
Contributor Author

jkomyno commented Sep 16, 2022

(flaky Mac OS compile check, restarted that on Buildkite)

Copy link
Contributor

@tomhoule tomhoule left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Let's just document where the names came from so we can track in which conditions these tables appear, etc. The list is growing and the risk of false positives is getting larger, we might want to enforce that postgis tables are in a separate schema and then ignore diffing that schema, we could do that with the multi-schema awareness. Or even ignore them conditionally based on the extensions declared in the datasource with the extensions proposal we are implementing. I'll open an issue.

@tomhoule
Copy link
Contributor

Here's the issue: prisma/prisma#15363

@jkomyno jkomyno merged commit fb56bfe into main Sep 17, 2022
@jkomyno jkomyno deleted the fix/migrate-prevent-deleting-postgis-columns branch September 17, 2022 10:29
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

Successfully merging this pull request may close these issues.

PostGis views access error
2 participants