Dave McCowan 9744f80186 Handle SQL Integrity Error More Generically ... SQL command with IntegrityError when any number of constraints fail to pass. These include checking for duplicates, checking for not null, or foreign key checks. Barbican was reporting these all as duplicates which can confuse debugging. This patch reports the error more accurately as an SQL constraint check failure. Change-Id: I7043fe01f949326b1e38c8f320ece8418f36acc4 Co-Authored-By: Dave McCowan <dmccowan@cisco.com> Closes-bug: #1489457		2017-03-06 15:48:40 +00:00
..
api	Update previous and next Consumer URLS in filtering	2017-02-02 16:59:00 +00:00
cmd	Merge "Adds true functional tests for db_manage script"	2017-02-01 13:07:17 +00:00
common	Handle SQL Integrity Error More Generically	2017-03-06 15:48:40 +00:00
hacking	Introduce hacking check to Barbican	2016-12-03 19:28:29 +08:00
locale	Imported Translations from Zanata	2016-10-19 10:40:51 +00:00
model	Handle SQL Integrity Error More Generically	2017-03-06 15:48:40 +00:00
plugin	Merge "Make error message clear when no supported secret store found"	2017-02-03 18:37:05 +00:00
queue	Merge "Remove translations for debug level log"	2016-11-30 10:47:56 +00:00
tasks	Merge "Remove translations for debug level log"	2016-11-30 10:47:56 +00:00
tests	Handle SQL Integrity Error More Generically	2017-03-06 15:48:40 +00:00
__init__.py	Files with no code must be left completely empty	2016-11-17 14:19:47 +08:00
context.py	Don't inspect oslo.context	2016-09-13 10:49:20 +10:00
i18n.py	Drop old namespace for some oslo libraries	2015-02-02 22:10:45 +02:00
version.py	Enable tag-based full version reporting via pbr	2014-01-22 18:01:30 -06:00