Feature Request: Support for PostGIS about sqlacodegen HOT 5 CLOSED

Original comment by Francisco Puga (Bitbucket: fpuga, GitHub: fpuga):

I think that this is duplicated to #18

from sqlacodegen.

any update on this issue?

from sqlacodegen.

I haven't worked on this library for a good while now. I made the mistake of starting the 2.0 refactoring before I had committed enough time to do it. I plan to make a number of improvements in the next couple weeks and make a new release too.

from sqlacodegen.

This fix doesn't work for me, I'm using a POLYGON and POINT type in mysql, and I get this error running latest sqlacodegen and geoalchemy:

venv/lib/python3.7/site-packages/sqlalchemy/dialects/mysql/reflection.py:181: SAWarning: Did not recognize type 'polygon' of column 'area'
  (type_, name))
venv/lib/python3.7/site-packages/sqlalchemy/dialects/mysql/reflection.py:181: SAWarning: Did not recognize type 'point' of column 'location'
  (type_, name))

I assume at this point it gives those fields null type and I get this error later in the code generation:

venv/lib/python3.7/site-packages/sqlalchemy/sql/compiler.py", line 2973, in visit_null
    "type on this Column?" % type_)
sqlalchemy.exc.CompileError: Can't generate DDL for NullType(); did you forget to specify a type on this Column?

from sqlacodegen.

What the commit fixed was PostGIS support. It doesn't do anything about the corresponding types on MySQL. If you can point out what needs to be imported first, then please create a new issue for that.

from sqlacodegen.