Task #10846 (new)
Opened 11 years ago
Last modified 9 years ago
Collect ChgrpValidation exceptions — at Version 3
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | critical | Milestone: | 5.x |
| Component: | Services | Version: | n.a. |
| Keywords: | fs | Cc: | fs@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | 1.5d |
| Sprint: | FS demo 4.x |
Description (last modified by jamoore)
When the first validation error (foreign key constraint) is encountered during graph processing, an exception is immediately thrown and the ID of the object causing the exception is returned in the constraints field of the omero::cmd::ChgrpERR object. Clients would benefit from having all the constraints rather than just the first such constraint.
Currently there is nothing in place to allow this type of detection. A possible workaround may be to perform a query (see #10782) before executing the chgrp.
See:
Change History (3)
comment:1 Changed 11 years ago by jburel
- Sprint changed from FS demo 4.2 to FS Demo 4.3
comment:2 Changed 11 years ago by jamoore
- Priority changed from blocker to critical
- Sprint changed from FS Demo 4.3 to FS demo 4.x
With Mark's work on #10782 / #10890, this should no longer be of significant impact. We may want to re-write the tests as a part of that work to not look for a constraint, but rather to perform the query. The constraint checks could be left in / turned back on as a double validation, once this ticket is handled.
comment:3 Changed 11 years ago by jamoore
- Description modified (diff)
Moved from sprint FS demo 4.2