Hello,

(I have a feeling this has something to http://hibernate.org/155.html and inverse="true/false", but would appreciate guidance with adding inverse='true/false" to the correct side of the relation)

Summary of the problem:
Saving one domain model POJO does not save (insert) another, required
domain model POJO.

Details:
2 tables: ACCOUNT & USER_INFO
2 domain model POJOs: Account & UserInfo

When saving UserInfo to USER_INFO table, no Account is inserted into
ACCOUNT table.


-- ACCOUNT:

id SERIAL
CONSTRAINT pk_account_id PRIMARY KEY,
username ....

-- USER_INFO:

id SERIAL
CONSTRAINT pk_user_info_id PRIMARY KEY ,
account_id INTEGER
CONSTRAINT fk_user_info_account_id REFERENCES account(id) ,
first_name ....


-- ACCOUNT.hbm.xml:

<one-to-one
name="userInfo"
class="com.example.model.UserInfo"
cascade="all"
outer-join="auto"
constrained="false"
property-ref="account"
/>

-- USERINFO.hbm.xml:

<many-to-one
name="account"
class="com.example.model.Account"
column="account_id"
not-null="true"
unique="true"
/>


-- JAVA CODE that does not 'do the right thing':

Account acct = getAccountFromSomewhere();
UserInfo uinfo = new UserInfo("John", ....);
uinfo.setAccount(acct);
// IMPORTANT: if I add the following line, then Account IS saved
// acct.setUserInfo(uinfo);
Session ses = getHibernateSessionFromSomewhere();
ses.save(uinfo);
ses.flush();
ses.connection().commit();
ses.close();


Thank you,
Otis

Please read http://www.hibernate.org/Documentation/InsideExplanationOfInverseTrue first and tell me if it answers your questions.

Hello Emmanuel,

Well, I read that document before posting (see the 155.html reference at the very top of my post). However, it looks like I have many-to-one, which is implicilty and invariably inverse="false" (quote from 155.html: "Note that <many-to-one> is always inverse="false" (the attribute does not exist).")

Does inverse="true/false" still apply here? That is, where would I have to place it for Account to get INSERTed before UserInfo?

Thanks,
Otis

Sorry I read your post too fast.
add cascade="save-update" in your many-to-one. Hibernate will then cascade account creation when saving user.