Hi all,

I'm reading the documentation of NHibernate in order to know if it fits to my needs.

I got objects from a webservice and I want to persist them to a database.

The class are generated from Visual Studio and I would prefer not to modify them.

At the start of my reading, NHibernate seemed to be perfect for my needs because it doesn't require to change the Business object, in my case the generated class from the webservice.

Then I have found this in the documentation about "Assigned Identifier" id generator ( my identifiers are retrieved from the webservice).



the SavorUpdate method was a method which really interests me since it's exactly what I have to do.

Does the last version of NHibernate always contain this limitation ?
is this change planned before the end of this month ( I have a short dead line) ?

Thanks in advance for your feedback

Regards

Christophe

I'm using 1.02 and SaveorUpdate does fail if you try to persist a new entity with a identity whose value is not the unsaved-value when the identity generator is of the assiged type. I explicity call Save for such objects.

Ok

Thanks for the information

AFAIK, NHibernate can also use a <version> attribute to distinguish betwwen saved/unsaved objects. See docs: http://www.hibernate.org/hib_docs/nhibernate/html/mapping.html#mapping-declaration-version

Gert

Ok

Thanks

I will look at this