User Story #857 (closed)
Opened 16 years ago
Closed 16 years ago
Delete service needed to simplify client usage
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | major | Milestone: | 3.0-Beta3 |
Component: | Services | Keywords: | delete, service |
Cc: | jburel, jrswedlow | Story Points: | n.a. |
Sprint: | n.a. | Importance: | n.a. |
Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
Currently it is quite difficult to delete an image requiring a query roughly of the form:
public final static String IMAGE_QUERY = "select i from Image as i " + "left outer join fetch i.pixels as p " + "left outer join fetch p.channels as c " + "left outer join fetch c.logicalChannel as lc " + "left outer join fetch c.statsInfo as sinfo " + "left outer join fetch p.planeInfo as pinfo " + "left outer join fetch p.thumbnails as thumb " + "left outer join fetch p.pixelsFileMaps as map " + "left outer join fetch map.parent as ofile " + "left outer join fetch p.pixelsDimensions as dim " + "left outer join fetch p.settings as setting " + "where i.id = :id";
which we obviously shouldn't require each client develoepr to enter.
There is an issue with exactly what the semantics are (to be defined here later), but we will most likely also want to allow for some customization of the delete process. (e.g. does a particular site want OriginalFiles to be deleted when an Image is deleted?)
See also : #587
Change History (2)
comment:1 Changed 16 years ago by jmoore
comment:2 Changed 16 years ago by jmoore
- Resolution set to fixed
- Status changed from new to closed
No word for or against. Closing. Either reopen or open specific tickets for API changes.
r2033 Has a fully working implementation. Leaving this open for further testing from the client-side, definition of the semantics, and possible API changes.