Task #12317 (closed)
Refactor deletion on map annotations
| Reported by: | mtbcarroll | Owned by: | mtbcarroll |
|---|---|---|---|
| Priority: | major | Milestone: | 5.1.0-m1 |
| Component: | ORM | Version: | n.a. |
| Keywords: | n.a. | Cc: | omero-team@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | 0.0d |
| Sprint: | n.a. |
Description (last modified by mtbcarroll)
At present there is Java code such that when an object with a map value property is deleted, first the HQL names are used in a SQL statement to remove the property's map entries, preventing a constraint violation. This would be better implemented as a SQL trigger in the generation template.
Change History (5)
comment:1 Changed 10 years ago by mtbcarroll
- Description modified (diff)
comment:2 Changed 10 years ago by mtbcarroll
- Owner changed from jamoore to mtbcarroll
comment:3 Changed 10 years ago by mtbcarroll
- Status changed from new to accepted
comment:4 Changed 10 years ago by mtbcarroll
- Resolution set to fixed
- Status changed from accepted to closed
comment:5 Changed 10 years ago by Josh Moore <josh@…>
- Remaining Time set to 0
(In [10f0f527deed157584d818a8cc8cb235026e3ca5/ome.git] on branch develop) Merge pull request #2893 from mtbc/trac-970-12317-dbpatch-and-map-value
fix #970, #12317: adjust dbpatch table; delete map values with triggers
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
The abovementioned map value deletion code was introduced as part of https://github.com/openmicroscopy/openmicroscopy/pull/2301