Task #2966 (new)
Opened 14 years ago
Last modified 8 years ago
Replace hard-coded NULL delete option for Pixels.relatedTo
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | Services | Version: | n.a. |
| Keywords: | n.a. | Cc: | jburel |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | 0.25d |
| Sprint: | n.a. |
Description
For 4.2.1, the logic for DeleteEntry.Op.NULL was hard-coded to mean only null Pixels.relatedTo if it pointed to the current Pixels being deleted.
Long-term, the NULL option should allow nulling any field which points to the current object being deleted, but this most likely requires a new syntax.
Change History (5)
comment:1 Changed 14 years ago by jmoore
comment:2 Changed 12 years ago by jmoore
- Milestone changed from Unscheduled to OMERO-4.4.2
- Sprint set to 2012-08-28 (3)
This will take place along with #6905.
comment:3 Changed 12 years ago by jmoore
- Owner set to jmoore
- Remaining Time set to 0.25
comment:4 Changed 12 years ago by jmoore
- Milestone changed from OMERO-4.4.3 to OMERO-4.5
- Sprint 2012-08-28 (3) deleted
comment:5 Changed 8 years ago by jamoore
- Milestone changed from 5.x to Unscheduled
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
(In [8198]) Hard-coded NULL handling of Pixels.relatedTo on delete (Fix #2776, See #2966)