On 7/5/14, 3:14 PM, Phillip Aquilina wrote: > I finally had a chance to try this with the inspector and quickly > discovered it doesn't support expression-based indexes with this > warning, "Skipped unsupported reflection of expression-based index > <some_index>." I can patch this out locally for my own needs but is > there a bigger reason this is not yet supported that I should be > worried about?
on the reflection side, expressions inside of indexes (which is largely a Postgresql thing) are skipped at the moment. This doesn't present any issues. It only means if you're using Alembic to autogenerate migrations, you might have to type these expressions into your migration file manually. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
