[EMAIL PROTECTED] wrote:
I've always (in OJB ODMG) used
cascading delete bounded by appropriate auto-delete settings; now it looks
as if I have no choice but to delete each individual object by hand. True?
Setting the cascading delete settings by relationship type (1:1, 1:n,
m:n) seems
Hi Steve,
[EMAIL PROTECTED] wrote:
Now I remember why I'm always hesitant to upgrade OJB - it seems like
there is some fundamental change to how things work.
we made a complete refactoring of the odmg implementation in 1.0.2/3,
because of the many known issues in OJB =1.0.1 (see release-notes
Martin Armin,
Thanks for the responses. Some more info:
- The collection in question is a non-decomposed m:n.
- There actually are two collections which exhibit this problem; in one
case the child pk is an int, and in the other it's a String. The keys are
not null or 0 (the child being
Three more things:
1) I have ImplicitLocking turned off
2) My pseudocode is wrong: Actually, the parent object is created in a
different transaction. So it's like this:
tx = odmg.newTransaction();
profile = new FieldOfficeProfileImpl();
database.makePersistent(profile);
[EMAIL PROTECTED] wrote:
Three more things:
1) I have ImplicitLocking turned off
2) My pseudocode is wrong: Actually, the parent object is created in a
different transaction. So it's like this:
tx = odmg.newTransaction();
profile = new FieldOfficeProfileImpl();
Sigh. Is it still Monday? I'll get it right eventually. Here is what is
(was) actually being done:
tx = odmg.newTransaction();
tx.begin();
profile = new FieldOfficeProfileImpl();
database.makePersistent(profile);
tx.commit();
tx = odmg.newTransaction();
[EMAIL PROTECTED] wrote:
Sorry for so much volume, but I spoke too soon.
The only thing that changes when I add tx.lock(county, tx.WRITE) is that
it does an update instead of an insert. In fact, it does this even if I
request a READ lock. So, in summary, this code:
tx =
Now I remember why I'm always hesitant to upgrade OJB - it seems like
there is some fundamental change to how things work. I hope things are
getting more stable, 'cause in the in-between times when I don't have to
rework, it's a great tool.
Here's where I'm stuck now. I just upgraded from
