[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[stellation-res] Checked in unittest code that reveals bug 25992
|
I'm working on unit tests for the ACL code using direct repository
access. In the process, I just uncovered a rather nasty bug in the
core repository itself.
In the updateBranchHead operation, the system performs updates of
the modified artifacts in the order in which they appear in the
list contained by the modifiedArtifacts parameter.
If any atomic artifacts precede compounds in this list, the update
operation will fail with a referential constraint error, because there
is a constraint on the Compounds table that the artifact record for
all members of the compound must exist. Since the new artifact hasn't
been inserted yet, the constraint fails. For details how to reproduce
this, see the bugzilla entry.
The fix for this would seem to be creating the artifact records for all
new artifacts first, and then calling the agents to do the storage of
the artifact contents.
-Mark
--
Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: mcc@xxxxxxxxxxxxxx ------- Personal Email: markcc@xxxxxxxxxxx
