[migration] Fix addition of entity type including boundary constraints on its own attributes This was failing because of the sequence of sql executing when adding an attribute: 1. add entity type <commit> 2. add relation type for attribute 1 <commit> 3. add attribute 1 and associated constraints <commit> etc. In the case of e.g. start/end constraint, we were trying to add the constraint before addition of the constrained attribute (e.g. add constraint on 'start' referencing 'end', but only 'start' has been added yet, not 'end'). This patch fix this by: * adding the relation type to the schema without having to commit, but keeping the operation to revert the addition if necessary - this allows to a single commit for all attributes of the entity type ; * using a LateOperation on constraint operation, so we ensure attributes are actually added before any constraint is added.

     1

^build$

     2

^dist$

     3

\.egg-info$

     4

^.tox$

     5

^.cache$

     6

\.pyc$

     7

\.pyo$

     8

\.bak$

     9

\.old$

    10

\~$

    11

\#.*?\#$

    12

\.swp$

    13

^doc/book/en/apidoc$

    14

\.old$

    15

\.pybuild

    16

debian/python-cubicweb

    17

debian/*.log

    18

debian/*.substvars

    19

debian/cubicweb-doc

    20

debian/cubicweb

    21

debian/files

    22

    23

syntax: regexp

    24

.*/data.*/database/.*

    25

.*/data/ldapdb/.*

    26

.*/data/uicache/

    27

.*/data/libpython/cubicweb_.*/i18n/.*\.po

    28

^doc/html/

    29

^doc/doctrees/

    30

^doc/book/en/devweb/js_api/

    31

^doc/_build

    32

^doc/js_api/

    33

test-results.xml