HI

Suppose I have two objects, A and B with a one-to-many mapping between them. So, I'd have the HBM mapping as:



and



Now, I can create a labBook object, add it to the array in the person object and save the person object - this in turn saves the labBook object automatically - provided the ID field in the labBook object IS NOT of "assigned" type.

But, if I try to create a person object, and associate it with a newly created labBook object and try to save the labBook object, it gives me an exception:



It asks me to save the person object first. Can I get the same effect as the first one I described (automatic save) in this case also? And 2ndly, is there any way to get this effect with the ID field defined as ASSIGNED?

Regards
Arijit

As an addendum to the previous topic: supposing I have a one-to-many relationship between a person and a labbook. If I delete one person object, would the associated labbook objects be deleted as well? It isn't working that way in practice though.....

Arijit

No, things have all messed up. Using the same mapping files described above (changed only the id part of the labBook object to assigned, as that is what I need), I can't get the child object (a labBook) saved when the parent (a person) is saved. I am getting the following error:

[java] Assgined LSID: urn:lsid:mygrid.org.uk:labbookview:5f3768eb80f094ea00e3849c4f914edb
[java] - Could not synchronize database state with session
[java] net.sf.hibernate.HibernateException: SQL insert, update or delete failed (row not found)
[java] net.sf.hibernate.HibernateException: SQL insert, update or delete failed (row not found)
[java] at net.sf.hibernate.impl.NonBatchingBatcher.addToBatch(NonBatchingBatcher.java:25)
[java] at net.sf.hibernate.impl.NonBatchingBatcher.addToBatch(NonBatchingBatcher.java:25)
[java] at net.sf.hibernate.persister.EntityPersister.update(EntityPersister.java:688)
[java] at net.sf.hibernate.persister.EntityPersister.update(EntityPersister.java:688)
[java] at net.sf.hibernate.persister.EntityPersister.update(EntityPersister.java:641)
[java] at net.sf.hibernate.persister.EntityPersister.update(EntityPersister.java:641)
[java] at net.sf.hibernate.impl.ScheduledUpdate.execute(ScheduledUpdate.java:52)
[java] at net.sf.hibernate.impl.ScheduledUpdate.execute(ScheduledUpdate.java:52)
[java] at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2382)
[java] at net.sf.hibernate.impl.SessionImpl.executeAll(SessionImpl.java:2382)
[java] at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2336)
[java] at net.sf.hibernate.impl.SessionImpl.execute(SessionImpl.java:2336)
[java] at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:2204)
[java] at net.sf.hibernate.impl.SessionImpl.flush(SessionImpl.java:2204)
[java] at net.sf.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:61)
[java] at net.sf.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:61)
[java] at uk.org.mygrid.mir.test.HibernateTest.createTestData(HibernateTest.java:142)
[java] at uk.org.mygrid.mir.test.HibernateTest.main(HibernateTest.java:249)
[java] at uk.org.mygrid.mir.test.HibernateTest.createTestData(HibernateTest.java:142)
[java] java.lang.RuntimeException: couldn't get connection
[java] at uk.org.mygrid.mir.test.HibernateTest.main(HibernateTest.java:249)
[java] at uk.org.mygrid.mir.test.HibernateTest.main(HibernateTest.java:255)
[java] Exception in thread "main"

Please give me some hints. I got to get past this issue.

Arijit

Hi Again

This is what I found: if I update these relations at the 1-end (in this example, the person object - i.e. add the labBooks in the array contained inside the person object), the cascade-delete is working when I delete a person object. But it doesn't work if I add a reference to the person object in the labBook object (and don't use the array on the other end).

If I don't save a labBook explicitly, and try to add it in the array and then save the parent person object, the cascade-save isn't working. I am getting the exception mentioned in the previous post.

Is this behaviour correct?

Arijit

The last error you posted is typically the result of HIbernate not knowing whether to send an update or insert, because it can't use your identifier to know that (normally if id==null, hib does an insert, otherwise, does an update)

To get around that prob, you could use the <timestamp> property....
basically tell hibernate to use a different field to determine if the object is new or existing.

James

Oops - that solved one part of the puzzle...thanx a ton James

Arijit