NHibernate: “collection was not processed by flush()” caused by lazy loading issue?

I think Nbernate throws this exception if the collection is dirty but the cascade setting does not cause the changes to be persisted.

I just want to make a new parent, with the same child as an existing parent. Cascade for hasone is saveupdate and for hasmany is alldeleteorphan – Andrew Bullock Jul 6 '10 at 17:20 Are you initializing the GrandChildren collection in Child's constructor? Please show the mappings.

– Jamie Ide Jul 6 '10 at 17:23.

You can use session. Load to reference an existing instance of Child without making a trip to the db. This should do it, I think: session.

Save(new Parent { Child = session. Load(existingParent.Child. Id) } ); But check to make sure that the .

Id call doesn't trigger a db trip.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.