Context Navigation

Changes between Initial Version and Version 3 of Ticket #14223

Ticket #14223
- Property Triage Stage Unreviewed → Accepted
- Property Has patch set
- Property Owner changed from nobody to Ramiro Morales
- Property Status new → assigned

initial	v3
1	1	It seems we aren't capturing the `<db api driver module>.IntegrityError` exceptions raised when `connection.commit() is executed` in the same way we do in `execute()`.
2	2
3		Found this while creating tests to verify FK constraint in sqlite (#14304). My `assertRaises(django.db.[utils.]IntegrityError, ...)` weren't being triggered and printing the exception type shows `<class 'pysqlite2.dbapi2.IntegrityError'>`. Same thing happens now with postgres (see below).
	3	Found this while creating tests to verify FK constraint in sqlite (#14204). My `assertRaises(django.db.[utils.]IntegrityError, ...)` weren't being triggered and printing the exception type shows `<class 'pysqlite2.dbapi2.IntegrityError'>`. Same thing happens now with postgres (see below).
4	4
5	5	The `DatabaseError` and `IntegrityError` unification was introduced in r12352, if this is confirmed as an issue it wouldn't be a regression in 1.2, but a 1.2 feature introduced in an incomplete fashion.