db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Armin Waibel (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (OJB-103) TransactionExt.flush() call doesn't clear 1:1, 1:n link history
Date Fri, 17 Mar 2006 12:19:31 GMT
     [ http://issues.apache.org/jira/browse/OJB-103?page=all ]
     
Armin Waibel resolved OJB-103:
------------------------------

    Fix Version: 1.0.5
     Resolution: Fixed

Now OJB clear the 1:1, 1:n FK link list on reuse of object entries

> TransactionExt.flush() call doesn't clear 1:1, 1:n link history
> ---------------------------------------------------------------
>
>          Key: OJB-103
>          URL: http://issues.apache.org/jira/browse/OJB-103
>      Project: OJB
>         Type: Bug
>   Components: ODMG-API
>     Versions: 1.0.4
>     Reporter: Armin Waibel
>     Assignee: Armin Waibel
>      Fix For: 1.0.5

>
> TransactionExt.flush() call doesn't clear 1:1, 1:n link history, thus OJB will reuse
the outdated link entries on commit or additional flush() calls again. This could cause side-effects
- see discussion here
> http://www.mail-archive.com/ojb-user%40db.apache.org/msg15043.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org


Mime
View raw message