Re: 1:m relation not updating

[Thomas Mahler]

You have to lock the b elements too if you are using normal collections 
to hold the many-side of the association.

If you were using DList as your collection class this won't be required.

cheers,
thomas
Saman Ghodsian wrote:
Hi there, 

Here is the situation...... Say I have class A and class B   1----->m

I created the repository.xml 

Everything works fine when storing A to DB with a couple of B's

Tx.lock(a, Transaction.WRITE);
Tx.Commit
Next step is to load a and add more B's and then save it again.....

I created the query..... And all a and the related B's get loaded ok....

Now I add a couple more B's 
And store a 

Tx.lock(a, Transaction.WRITE);
Also tried 
Tx.lock(a, Transaction.UPGRADE);

But the new B's don't get inserted in DB.....
Any ideas????
Thanks



Sam

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]