Hibernate version:
2.1.6

Mapping documents:

Code between sessionFactory.openSession() and session.close():

Full stack trace of any exception that occurs:

Name and version of the database you are using:

Debug level Hibernate log excerpt:

Hi,

Question from a newbie. The hibernate docs seem to suggest to use a many-to-one to map an association to another class reference (even if that reference really represents a one-to-one association. Can folks confirm this is in fact the way to go?

Secondly, having done the mapping using a many-to-one element to map an assoication with another class. I notice that Hibernate does not attempt to "walk" across this association and persist the associated class. Shouldn't hibernate have the smarts to "walk" across all the different associations mapped this way and attempt to do the persistence (of course I have mappings for all the classes from the associated classes). Is there an attribute or some flag or some option I need to flick on to enable this behaviour. Or do I really have to persist all the associated classes programatically in the context of a hibernate transaction?

Thanks in advance,
Ali

Confirmed, you can use many-to-one for a foreign key one-to-one mapping. "Works for me."

And yes, you apparently have to insert the dependent first.

To your second question: Have a look at cascade styles. E.g. cascade save-update on an association means that the associated objects are also saved or updated.

Reto

Gack, My bad, yes, if you cascade='all', then it will automagically save the assocaited object. I didn't write my test properly!

no you don't, that's what hibernate is there for.

maybe post your mapping docs.

thanks all folks, this info has been really helpful, much appreciated, cascade seems to be the way to go. Thx.