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

# copyright 2003-2010 LOGILAB S.A. (Paris, FRANCE), all rights reserved.

     2

# contact http://www.logilab.fr/ -- mailto:contact@logilab.fr

     3

#

     4

# This file is part of CubicWeb.

     5

#

     6

# CubicWeb is free software: you can redistribute it and/or modify it under the

     7

# terms of the GNU Lesser General Public License as published by the Free

     8

# Software Foundation, either version 2.1 of the License, or (at your option)

     9

# any later version.

    10

#

    11

# CubicWeb is distributed in the hope that it will be useful, but WITHOUT

    12

# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS

    13

# FOR A PARTICULAR PURPOSE.  See the GNU Lesser General Public License for more

    14

# details.

    15

#

    16

# You should have received a copy of the GNU Lesser General Public License along

    17

# with CubicWeb.  If not, see <http://www.gnu.org/licenses/>.

    18

""" CW - nevow/twisted client

    19

    20

"""