[massive store] Use a slave specific table for relation insertion in the massive store * attribute a random id to the store * add a column containing this id in the cwmassive_initialized table * separate generic `master_init` which create the cwmassive_initialized table from rtype specific initialization which must be done in each slave now * delay removal of table indexes to `finish` * get back relations from each table on `finish` Similar work still has to be done for entities insertion - which will allow more cleanup to the constraints handling which is still rough for now. Related to #15538303

     1

[MASTER]

     2

load-plugins=cubicweb.pylintext

     3

ignore=__pkginfo__

     4

     5

[MESSAGES CONTROL]

     6

disable = too-many-ancestors,too-many-instance-attributes,too-many-public-methods,

     7

      too-few-public-methods,too-many-arguments,import-error

     8

     9

[BASIC]

    10

function-rgx = [a-z_][a-z0-9_]{2,35}$

    11

good-names=w,_

    12

    13

[TYPECHECK]

    14

generated-members=debug,info,notice,warning,error,critical,exception

    15

    16

[CLASSES]

    17

exclude-protected=_cw,_cnx,

    18

      # namedtuple public API.

    19

      _asdict,_fields,_replace,_source,_make

    20

    21

    22

[FORMAT]

    23

max-line-length=100

    24

max-module-lines=2000