Option to ignore tables

[agronholm]

Originally reported by: Ishan Khare (Bitbucket: ishan_khare, GitHub: Unknown)

---

just like the --tables option which specifies the tables to be processed, there should be a --skip-tables option. This will be particularly helpful if i have only a few tables to skip among lots of tables.

---

• Bitbucket: https://bitbucket.org/agronholm/sqlacodegen/issue/37

[agronholm]

Couldn't you just remove the unwanted tables from the output?

[emattiza]

Agreed!

[gmonkman]

Couldn't you just remove the unwanted tables from the output?

Also posted against #39.

Unsupported data types cause sqlacodegen to fail without producing any output. My example is spatial datatypes (geography and geometry) in MSSQL.

I still want to use SQLAlchemy for almost all my CRUD. I can hand roll my own CRUD for tables with spatial data, but it would be nice to be able to dump the model for most of my DB using sqlacodegen.

[agronholm]

It would seem that the right solution then is for sqlacodegen to automatically skip tables it cannot handle. Agreed?

[agronholm]

Also, if you can point me to a library which adds those geography/geometry types to MSSQL, I'd be happy to add a conditional import for that.

[gmonkman]

It would seem that the right solution then is for sqlacodegen to automatically skip tables it cannot handle. Agreed?

Ta, perfectly great for me. Would need some sort of feedback to user letting them know why the table was skipped.

Also, if you can point me to a library which adds those geography/geometry types to MSSQL, I'd be happy to add a conditional import for that.

The geoalchemy project would appear to add sqlalchemy support for MSSQL spatial datatypes but is not supported for Python >2.6.

The geoalchemy2 project, unfortunately does not support MSSQL, only PostGIS/Postgresql

Not found anyother liibraries to support MSSQL spatial types in SQLAlchemy.

[agronholm]

Ta, perfectly great for me. Would need some sort of feedback to user letting them know why the table was skipped.

That's what I'll do then, assuming there are no problems with this approach coming from the sqlalchemy reflection process itself (which I do not control).

Not found anyother liibraries to support MSSQL spatial types in SQLAlchemy.

Are those types native to MSSQL? If they are, then it would be best to file a PR against SQLAlchemy itself.

[gmonkman]

Are those types native to MSSQL? If they are, then it would be best to file a PR against SQLAlchemy itself.
Yes, native types since sql server 2008. Will do. Thanks.

[gmonkman]

So are they native to MSSQL or not?

Yup, since MSSQL 2008.