misc/migration/3.17.11_Any.py
author Christophe de Vienne <cdevienne@gmail.com>
Wed, 30 Apr 2014 08:07:59 +0200
changeset 9720 a7210c912507
parent 9463 d62e13eba033
permissions -rw-r--r--
[req.find] Use vreg.schema.eschema for eschema lookup If an etype is non-existant, using vreg.schema[etype] raises a confusing error complaining about a non-existing relation. This is because of the implementation of vreg.schema.__getitem__ that look first in entities and then in relations. Using directly vreg.schema.eschema restrict the lookup to etypes only, hence raises a meaningful error when the etype does not exist.

for table, column in [
        ('transactions', 'tx_time'),
        ('tx_entity_actions', 'tx_uuid'),
        ('tx_relation_actions', 'tx_uuid')]:
    repo.system_source.create_index(session, table, column)

commit()