cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Zeigler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAY-1397) ROP: Missing the COMMIT state when deleting HOLLOW object
Date Wed, 24 Feb 2010 16:30:28 GMT

    [ https://issues.apache.org/jira/browse/CAY-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837856#action_12837856
] 

Robert Zeigler commented on CAY-1397:
-------------------------------------

I'm not sure this is a bug?

HOLLOW => object is backed by a persistent row, but hasn't been fully fetched yet (just
the id)
COMMIT => the state just after a commit, before any additional modifications (including
delete) occur
DELETED => the state when an object has been marked for deletion.

If you've just fetched the id of an object, it's not COMMIT, it's HOLLOW. If you then mark
the object for deletion without performaing any action first that would trigger the resolution
of the object's properties, it shouldn't ever be in the COMMIT state; it should be DELETED.


What behavior are you trying to implement that requires a DELETED object to first be resolved?

> ROP: Missing the COMMIT state when deleting HOLLOW object
> ---------------------------------------------------------
>
>                 Key: CAY-1397
>                 URL: https://issues.apache.org/jira/browse/CAY-1397
>             Project: Cayenne
>          Issue Type: Bug
>          Components: ROP
>    Affects Versions: 3.0RC2
>            Reporter: Ksenia Khailenko
>
> When deleting persistent object at HOLLOW state, it changes the state to DELETED without
resolving 

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


Mime
View raw message