Account for new psycopg2 exception classes mapping From psycopg2 >= 2.8, specific exceptions are raised corresponding to postgresql errors. E.g. a CheckViolation exception is raised instead of a generic IntegrityError previously when a constraint violation occurs. The way we intercept database errors, especially for constraint violation, is not compliant with that because we do not catch subclasses of IntegrityError in native source's doexec() method. We fix this by checking for the presence of IntegrityError error in exception class's mro. This is still overcomplicated and clumsy, because we still use string comparison, but this is the best we can do as far as I know. (A better fix would be 'isinstance(ex, IntegrityError)' but we have no engine-independent error classes, so this is not possible. Something like sqlalchemy's DBAPI Errors [1] might help: https://docs.sqlalchemy.org/en/latest/errors.html#dbapi-errors)

     1

Document: cubicweb-doc

     2

Title: CubicWeb Documentation

     3

Author: Logilab

     4

Abstract: Some base documentation for CubicWeb users and developpers

     5

Section: Apps/Programming

     6

     7

Format: HTML

     8

Index: /usr/share/doc/python-cubicweb-documentation/html/index.html

     9

Files: /usr/share/doc/python-cubicweb-documentation/html/*