Re: [sqlalchemy] Re: Composite index using naming convention

On Thu, May 17, 2018 at 9:58 AM, HP3 wrote: >> Thanks again Mike > > Especially for the 63 chars length warning!!! that is also the longest length of all the databases, Oracle is at like 30 or something, so this is why the naming conventions are not oriented around

Re: [sqlalchemy] Re: Composite index using naming convention

> > Thanks again Mike Especially for the 63 chars length warning!!! -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See

Re: [sqlalchemy] Re: Composite index using naming convention

On Wed, May 16, 2018 at 6:59 PM, HP3 wrote: > Thank you Mike, > > But I just noticed that the index name is not showing all the columns used > in the composition. > > CREATE INDEX ix_mymodel_prop_a ON mymodel (prop_a, prop_b) > > I was expecting: > > CREATE INDEX

[sqlalchemy] Re: Composite index using naming convention

Thank you Mike, But I just noticed that the index name is not showing all the columns used in the composition. CREATE INDEX ix_mymodel_prop_a ON mymodel (prop_a, prop_b) I was expecting: CREATE INDEX ix_mymodel_prop_a_prop_b ON mymodel (prop_a, prop_b) In my case, it failed because