-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
migrate dev
and PostGis Views
#7764
Comments
We can add more exceptions in migrate. Thanks for raising this. |
Ok I researched this and geometry_columns and spatial_ref_sys used to be tables, but they are views in newer versions of postgis. We have code to ignore these, it just needs to be extended to views. Working on this. |
spatial_ref_sys and geometry_columns used to be tables managed by postgis, and in more recent versions they are views managed by postgis. We make sure to ignore them in both cases. closes prisma/prisma#7764
spatial_ref_sys and geometry_columns used to be tables managed by postgis, and in more recent versions they are views managed by postgis. We make sure to ignore them in both cases. closes prisma/prisma#7764
@tomhoule was this released? I am getting this error on prisma 4.0.0
|
Should I open a new issue or can you reopen this one @tomhoule ? |
@capaj please open a new issue, it's a different view from those that were in the postgis docs we based the fix on (https://postgis.net/docs/manual-1.4/ch04.html#id41859) |
created as #14182 |
Bug description
Hi there, i am having difficulties running prisma migrate dev on a postgres db with postgis installed.
Looking at past issues with PostGis (#4745), spatial_ref_sys looks like is properly ignored now. But i also have in my database "geometry_columns" and "geography_columns" views which prisma migrate cannot seem to do anything about.
Unfortunately i cannot remove the PostGis extension. (ps. i am new to postgis and it is also possible that i have configured PostGis wrongly, as there doesnt seem to be anyone with the same issue)
Is there any place i can define a list of ignored tables / views for migrate?
How to reproduce
Expected behavior
No response
Prisma information
Running
prisma migrate dev --name init
Environment & setup
Prisma Version
The text was updated successfully, but these errors were encountered: