Nhibernate One-to-one mapping issue with child object insert error

Question

i\'ve being banging my head against the desk all day with the following Nhibernate problem.

Each bank account has one (and only one) set of rates associated with it.

Answer 1

One quick way around this would be to make the BankAccountId nullable. NHibernate should insert a record in the BankAccount table with a null id, then update the id.

In the past I've stumbled on a way to make it do the initial insert with the correct id instead of null. Unfortunately, I can't for the life of me remember what I changed.