[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
.. _cwvreg_module:
:mod:`cubicweb.cwvreg`
======================
.. automodule:: cubicweb.cwvreg
.. autoclass:: CWRegistryStore
:show-inheritance:
:members:
:undoc-members:
.. autoclass:: CWRegistry
:show-inheritance:
:members: schema, poss_visible_objects, select
.. autoclass:: InstancesRegistry
:show-inheritance:
:members:
.. autoclass:: ETypeRegistry
:show-inheritance:
:members:
.. autoclass:: ViewsRegistry
:show-inheritance:
:members:
.. autoclass:: ActionsRegistry
:show-inheritance:
:members:
.. autoclass:: CtxComponentsRegistry
:show-inheritance:
:members:
.. autoclass:: BwCompatCWRegistry
:show-inheritance:
:members:
:mod:`logilab.common.registry`
==============================
.. automodule:: logilab.common.registry