[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
.. _dataimport_module:
:mod:`cubicweb.dataimport`
==========================
.. automodule:: cubicweb.dataimport
Utilities
---------
.. autofunction:: count_lines
.. autofunction:: ucsvreader_pb
.. autofunction:: ucsvreader
.. autofunction:: callfunc_every
.. autofunction:: lazytable
.. autofunction:: lazydbtable
.. autofunction:: mk_entity
Sanitizing/coercing functions
-----------------------------
.. autofunction:: optional
.. autofunction:: required
.. autofunction:: todatetime
.. autofunction:: call_transform_method
.. autofunction:: call_check_method
Integrity functions
-------------------
.. autofunction:: check_doubles
.. autofunction:: check_doubles_not_none
Object Stores
-------------
.. autoclass:: ObjectStore
:members:
.. autoclass:: RQLObjectStore
:show-inheritance:
:members:
.. autoclass:: NoHookRQLObjectStore
:show-inheritance:
:members:
.. autoclass:: SQLGenObjectStore
:show-inheritance:
:members:
Import Controller
-----------------
.. autoclass:: CWImportController
:show-inheritance:
:members: