I have got a talbe that contains movements of modifications. So, this object/class can be updated never. How Can I indicate this situation to NHibernate?

So, This is, when I add a movement into a entity collection I want that it always is inserted when I execute SaveOrUpdate method from entity.

Example -->

entity.movemets.Add(new Movement(...));
session.SaveOrUpdate(entity);

result is-->
UPDATE ENTITY WHERE...
UPDATE MOVEMENTS WHERE ...

I would like me that the result is:
UPDATE ENTITY WHERE...
INSERT INTO MOVEMENTS VALUES....

the problem is that movement class has a composite-id primary key. So, I can't set unsaved-value. I've tried with version attribute, however, when I execute session.SaveOrUpdate(entity) hibernate only generates:

INSERT INTO MOVEMENTS...
it doesn't generates an UPDATE ENTITY sentence.

What about this situation, please?

As you can understand movement object only can be inserted.

Thanks for all.

Just an idea (and a bit of a hack)... I would think you can use the <sql-update> element in your class mapping to override the default update SQL generated; just make sure the statement you give in <sql-update> does not actually update anything. I have not tried this myself.

There are other things you can do to the objects to make sure the properties are not updatable. That is, create a public parameterized constructor, a private default constructor (for NHibernate), and make all properties are get-only; this makes sure any retrieved objects are not updatable.

I've token the decision of implement a Interceptor as:



So, I believe that if IsUnsaved function returns

true -> tells NH to do an insert
false -> tells NH to do an update
null -> use default ("is-unsaved" value)

The problem is that when an entity is savedOrUpdated doesn't generates SQL statement. I thought that if IsUnSaved method returns null, NHibernate will use unsaved-value decision.

For example,


when I execute session.saveOrUpdate(entity), hibernate only generates
INSERT INTO MOVEMENTS VALUES(...) and It should generates :

UPDATE ENTITY ... and an INSERT INTO MOVEMENTS statements

And if I don't add a movement into entity, entity is updated correctly,
So, if I execute
entity = session.get_entity(id);
entity.Location = new Location;
session.saveOrUpdate(entity);

NHibernate generates an UPDATE ENTITY SET ... statement correctly.

What Do I do wrong?

Thanks for all.

Can you post your mapping file please?

NHibernate shouldn't actually generate any SQL on SaveOrUpdate(), only on Flush. The reason you see some INSERTs is probably that your Moviments use identity identifier generation so NHibernate has to insert them right away but this is an exception, not the rule.