[massive store] Rework constraint/index handling The basic idea is to keep the primary constraint on entities.eid since it's heavily used in metadata insertions. Other option would have been to drop / recreate but its very costly on big database, and the index is used for insertion into the entities table itself, so it's not worth droping it at a first glance. Also, keeping it avoids to systematically drop all constraints which depends on it. We may thus now lazily drop constraints, only on insertion of some etype/rtype for the related table. Related to #15538359

     1

.. _urlrewrite_module:

     2

     3

:mod:`cubicweb.web.views.urlrewrite`

     4

=======================================

     5

     6

.. automodule:: cubicweb.web.views.urlrewrite

     7

     8

    .. autoclass:: URLRewriter

     9

        :show-inheritance:

    10

        :members:

    11

    12

    .. autoclass:: SimpleReqRewriter

    13

        :show-inheritance:

    14

        :members:

    15

    16

    .. autoclass:: SchemaBasedRewriter

    17

        :show-inheritance:

    18

        :members: