-
Notifications
You must be signed in to change notification settings - Fork 150
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
Does this work with postgis version 3? #691
Comments
This might be a bug in |
Thank you for the quick response @fantix |
Just submitted a commit to fix the error message, but the real issue is geoalchemy will execute statements after table creation using events in the synchronous way. code I don't see any easy and clean way to fix this, sadly. |
It anyway a better choice to use migrations with alembic. And it works properly with alembic and it also removes the necessity of using |
Yep. To replace psycopg2 completely, we'll need to do that for everything in the system. Much effort. If no objection, I think we can close this issue. |
Sure. I think it'd be a good idea to mention this issue somewhere if possible. Maybe in the docs or somewhere appropriate. |
It is mentioned that |
Oh! My bad. It's exactly what should be written. |
Closing |
Does this work with postgis version 3?
db.gino.create_all()
created the tables but skipped the columngeom_point = db.Column(Geometry('POINT'), nullable=True)
.I tried again, after dropping and re-creating the database.
Here is the stacktrace:
Originally posted by @diptangsu in #627 (comment)
The text was updated successfully, but these errors were encountered: