Duplicate entry error message does not always specify the relevant unique keys
Bug #1756443 reported by
Bob Haddleton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
Medium
|
Bob Haddleton |
Bug Description
When creating a workbook/
This change will update the DBDuplicateEntry error messages to always provide the keys and values that are causing the errors.
Changed in mistral: | |
assignee: | nobody → Bob Haddleton (bob-haddleton) |
Changed in mistral: | |
importance: | Undecided → Medium |
Changed in mistral: | |
milestone: | none → rocky-1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/553910
Review: https:/