misc/migration/3.18.2_Any.py
author Christophe de Vienne <cdevienne@gmail.com>
Wed, 30 Apr 2014 08:07:59 +0200
changeset 9720 a7210c912507
parent 9420 3809e93c33b8
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.
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
9420
3809e93c33b8 [schema] execute the new stored procs/funcs at migration time (closes #3450368)
Aurelien Campeas <aurelien.campeas@logilab.fr>
parents:
diff changeset
     1
install_custom_sql_scripts()
3809e93c33b8 [schema] execute the new stored procs/funcs at migration time (closes #3450368)
Aurelien Campeas <aurelien.campeas@logilab.fr>
parents:
diff changeset
     2
commit()