Hi,

I have a query concerning unsurprisingly NHibernate. The problem is ths.

I have a class named Recipe. A Recipe has a collection of attribues. In my mapping file this is defined as:



My question is what is the best way of persisting this collection without having to load the many to many class from the database for each attribute?

If I do the following:



NHibernate thinks that att is a new object and tries to save this instance to the database.

The only way I can get this to work is to load the Attribute object from the database and then add it to the Recipe's attribute collecction and then save it.

This seems inefficient.

Can anyone tell me a better way?

Cheers

Paul

I have quite a complex structure with composite-elements that contain many-to-one classes etc.

It is an ASP.NET app. so my only way would be to cache the lookups or something like that. I cannot use second level caching because it is a web farm and the MemCache is

Is there no way to tell NHibernate that the object is not to be saved to the db. The only way seems to pull it from the Session via loading it from the db.

I will have to do a lot of loading in order to persist it.

How do people generally approach this situation.