[Sqlalchemy-tickets] Issue #3989: MetaData.naming_convention support for composite indexes/foreign
Brought to you by:
zzzeek
From: whereswalden <iss...@bi...> - 2017-05-12 21:08:00
|
New issue 3989: MetaData.naming_convention support for composite indexes/foreign keys https://bitbucket.org/zzzeek/sqlalchemy/issues/3989/metadatanaming_convention-support-for whereswalden: Currently, [MetaData.naming_convention](http://docs.sqlalchemy.org/en/latest/core/metadata.html#sqlalchemy.schema.MetaData.params.naming_convention) does not support composite indexes or foreign keys, so those must be named explicitly. It'd be nice to be able to provide a template for those to be automatically named as well. It would likely be necessary for users to define a function to provide the name, since the constraint/index could include any number of columns, but a fairly simple example could be provided in the documentation that simply `','.join()`s the column names. |