fix optimisation with super session that may lead to integrity loss at some point I've decided to stop ensuring ?1 cardinality was respected when adding a new relation using a super session, to avoid the cost of the delete query. That was yet discussable because it introduced unexpected difference between execute and unsafe_execute, which is imo not worth it. Also, now that rql() in migration script default to unsafe_execute, we definitly don't want that implicit behaviour change (which already cause bug when for instance adding another default workflow for an entity type: without that fix we end up with *two* default workflows while the schema tells we can have only one. IMO we should go to the direction that super session skip all security check, but nothing else, unless explicitly asked.

     1

include README

     2

include pylintrc

     3

include bin/cubicweb-*

     4

include man/cubicweb-ctl.1

     5

     6

recursive-include doc *.txt *.zargo *.png *.html makefile *.rst

     7

     8

recursive-include misc *

     9

    10

recursive-include web/data *

    11

recursive-include web/wdoc *.rst *.png *.xml ChangeLog*

    12

    13

include web/views/*.pt

    14

    15

recursive-include etwist *.xml *.html

    16

    17

recursive-include i18n *.pot *.po

    18

recursive-include schemas *.py *.sql.*

    19

    20

recursive-include entities/test/data *

    21

recursive-include sobjects/test/data *

    22

recursive-include server/test/data *

    23

recursive-include server/test sources*

    24

recursive-include web/test/data *.js *.css *.png *.gif *.jpg *.ico external_resources

    25

recursive-include devtools/test/data *

    26

    27

recursive-include skeleton *.py *.css *.js *.po compat *.in *.tmpl

    28

    29

prune misc/cwfs