-
Notifications
You must be signed in to change notification settings - Fork 232
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
Did not recognize type 'geometry' on Postgresql with PostGIS #18
Comments
Original comment by Neil Albrock (Bitbucket: neilalbrock, GitHub: neilalbrock): I've recently encountered this issue as well. With SQLAlchemy 0.9.9 I get the following:
With the latest SQLAlchemy 1.0.4 I get this:
I hope that helps, it would certainly be good if all Postgres column types could be handled. Let me know if I can offer any assistance. |
Original comment by Francisco Puga (Bitbucket: fpuga, GitHub: fpuga): I also think that will be great to be able to create models with the geometry type ( I'm using sqlacodegen==1.1.6, SQLAlchemy==1.0.11, GeoAlchemy2==0.2.6. When using this tool a get:
The rest of the models are correctly created but for the 'geometry' columns NullType is used.
It's not a big deal, just search for NullType and replace with the correct values. But it will be useful that sqlacodegen can get the custom types from geoalchemy |
Closing this as it is superseded by #29. |
Originally reported by: rah lee (Bitbucket: rajanski, GitHub: rajanski)
Hi Am I doing something wrong or does sqlacodegen not work for PostGIS-enabled Postgresql databases
The text was updated successfully, but these errors were encountered: