that is kind of a bug for the time being. You'd need to name those constructs explicitly or exclude them using an include_object routine (see http://alembic.readthedocs.org/en/latest/api/runtime.html#alembic.runtime.environment.EnvironmentContext.configure.params.include_object)
On 12/27/2015 02:12 PM, Jonathan Beluch wrote: > I'm having a problem with indexes whose name is longer than > max_identifier_length and the comparisons during --autogenerate. > > The index on the code/metadata side is being compared using its > auto-generated naming convention name, which doesn't take into account > the max_identifier_length since that happens during compilation. > However, the index pulled from the DB has the _xxxx hash suffix in the > name. So auto generate will always output a drop_index/create_index pair. > > Any thoughts on how to solve this? Was thinking about something in > include_object and compiling things and/or a regex for the indexes > pulled from the db but both seem a bit hacky. > > Thanks. > > SQLAlchemy==1.0.11 > alembic==0.8.4 > postgres 9.4 > > -- > You received this message because you are subscribed to the Google > Groups "sqlalchemy-alembic" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to sqlalchemy-alembic+unsubscr...@googlegroups.com > <mailto:sqlalchemy-alembic+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sqlalchemy-alembic" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy-alembic+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
