Re: [Sqlalchemy-tickets] [sqlalchemy] #2915: Different database backend raise different exceptions on not null constraint violations

[sqlalchemy <mi...@zz...>]

#2915: Different database backend raise different exceptions on not null
constraint violations
-----------------------------------+------------------------------------
      Reporter:  guidow            |      Owner:  zzzeek
          Type:  defect            |     Status:  closed
      Priority:  medium            |  Milestone:
     Component:  engine            |   Severity:  no triage selected yet
    Resolution:  wontfix           |   Keywords:
Progress State:  completed/closed  |
-----------------------------------+------------------------------------
Changes (by zzzeek):

 * status:  new => closed
 * resolution:   => wontfix
 * status_field:  awaiting triage => completed/closed


Comment:

 unfortunately this is a situation of the DBAPI specification and is not
 within SQLAlchemy's power to fix - only if SQLAlchemy were to add massive
 translation layers for every exception possible raised by every database
 backend, which would be very error prone and make things a lot worse.   We
 propagate DBAPI exceptions as is (with additional information about
 context) in order to maximize transparency about what went wrong.

--
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2915#comment:1>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python