[schema] restore constraint checking when running on old sqlite Old sqlite3 doesn't provide CHECK constraint names in error messages, preventing us from translating a backend integrity error into a ValidationError. This was added in 2012, but the sqlite3 version in RHEL6 is older; so if we run on old sqlite, keep checking the constraints in python rather than only in SQL. Closes #10927494

     1

Release notes

     2

-------------

     3

     4

.. toctree::

     5

    :maxdepth: 1

     6

     7

    3.22

     8

    3.21

     9

    3.20

    10

    3.19

    11

    3.18

    12

    3.17

    13

    3.16

    14

    3.15

    15

    3.14