[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

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

     2

 Changelog history

     3

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

     4

     5

.. include:: 3.22.rst

     6

.. include:: 3.21.rst

     7

.. include:: 3.20.rst

     8

.. include:: 3.19.rst

     9

.. include:: 3.18.rst

    10

.. include:: 3.17.rst

    11

.. include:: 3.16.rst

    12

.. include:: 3.15.rst

    13

.. include:: 3.14.rst