On Wed, May 16, 2018 at 6:59 PM, HP3 <henddher.pedr...@gmail.com> 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 ix_mymodel_prop_a_prop_b ON mymodel (prop_a, prop_b)
>
> In my case, it failed because `prop_b = Column(..., index=True)`
>
> Perhaps the convention could be defined to account for multiple columns?
>
> Could I call the naming convention explicitly?
>
> Index(Meta.naming_convention.generate_name(...), MyModel.prop_a,
> MyModel.prop_b)
you can do something like this:
class IxConvention(object):
def __mod__(self, other):
return "ix_%s_%s" % (
other.const.table.name,
"_".join(col.name for col in other.const.columns)
)
convention = {
"ix": IxConvention(),
"uq": "uq_%(table_name)s_%(column_0_name)s",
"ck": "ck_%(table_name)s_%(constraint_name)s",
"fk": "fk_%(table_name)s_%(column_0_name)s_%(referred_table_name)s",
"pk": "pk_%(table_name)s"
}
but you're going to run out of characters if you have many column
names that are long, those identifiers only go up to 63 chars max on
Postgresql which you can use up quite quickly.
>
>
>
> On Wednesday, May 16, 2018 at 3:42:53 PM UTC-5, HP3 wrote:
>>
>> Hello:
>>
>> How can one create a composite Index whose name follows the naming
>> convention declared in Meta?
>>
>> We are using naming convention for all ORMed classes per
>> http://docs.sqlalchemy.org/en/latest/core/constraints.html#configuring-constraint-naming-conventions
>> but explicit Index'es end up with arbitrary names - not following the
>> convention.
>>
>> class MyModel(Base):
>> __tablename__ = 'mymodel'
>> ...
>> prop_a = Column(...)
>> prop_b = Column(...)
>>
>> Index('myindex', MyModel.propa, MyModel.prop_b) # arbitrary name 'myindex'
>>
>> Thanks
>>
>>
>>
>>
> --
> 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 http://stackoverflow.com/help/mcve for a full
> description.
> ---
> 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 https://groups.google.com/group/sqlalchemy.
> For more options, visit https://groups.google.com/d/optout.
--
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 http://stackoverflow.com/help/mcve for a full description.
---
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 https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
