db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew T. Adams (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JDO-469) Delete by object id
Date Fri, 23 Mar 2007 16:03:32 GMT

     [ https://issues.apache.org/jira/browse/JDO-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Matthew T. Adams resolved JDO-469.

    Resolution: Won't Fix

After discussion, the implementation is nothing more than
pm.deletePersistent(pm.getObjectById(oid, false))
which is not worth doing.

> Delete by object id
> -------------------
>                 Key: JDO-469
>                 URL: https://issues.apache.org/jira/browse/JDO-469
>             Project: JDO
>          Issue Type: Improvement
>          Components: api2, api2-legacy, specification
>    Affects Versions: JDO 2 maintenance release 1
>            Reporter: Matthew T. Adams
>         Assigned To: Matthew T. Adams
>             Fix For: JDO 2 maintenance release 1
> Currently, Query & PersistenceManager allow a user to get by query and by object
id, respectively.  However, symmetry is broken in the case of deletion:  you can delete by
query, but you cannot delete by object id.  The result is that you are forced to use a query
or load each object that you want to delete.  I noticed this asymmetry when I came across
a use case where I had the object id and wanted to delete by id without having to load the
object or construct a query.
> Why don't the following PersistenceManager methods exist?
> void deleteObjectById(Class cls, Object key);
> void deleteObjectById(Object oid);
> void deleteObjectsById(Collection oids);
> void deleteObjectsById(Object[] oids);
> Can we add these?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message