Hi,

I have a table and I only want to allow inserts and reads from it. at the application layer. I want to prevent row updates and deletes. I want the restriction at the application layer because I will allow some other applications to perform updates or deletes.

Is there anyway to define such restriction in the hibernate mapping file for a given persistent class? Can hibernate throw an exception when the application tries to commit an update or delete operation on a persistent object?

Thanks,
Ali

There are many different ways of doing this.

1. You could write PreUpdate and PreDelete event listeners: see ref docs section 12.2, "Event system".
2. You could write an Interceptor and implement the onDelete and onSave methods. This is in section 12.1. "Interceptors">
3. You could add update="false" to all properties, associations and collections in the class' mapping. Note that this will be a silent no-update/delete, you won't get an exception.
4. You could add update="false" to all collections/associations to this class from other mappings. As before, you won't get a warning when an update is attempted, it just won't happen.

There are upsides and downsides to each of these choices. Read the docs to find out which one (or which combination) is right for you.

Maybe I am being incredibly dumb/blind - but I dont see any way to set update="false" on collections....

Can anyone confirm that Im either correct or a dumbass?

I really want to suppress the "update" of collections when I update a previously detached object. I know those collections will never change after the initial save....

Cheers,
Nick

You are correct. I was misremembering the addition of the mutable attribute to collections. insert/update attributes has never been added to collections.

Ok.. thats that settled.

(TBH though, Id have preferred to be found to be a dumbass ... Id kinda like this tuning)

I take it, the absence of update/insert specification for collections is because its nasty? (or is it, in fact planned?)

Cheers.

More likely, noone has requested it. If mutable="false" is possible, and mutable="false" is the same as insert="false" update="false", then I can see no reason not to allow insert/update attributes.

Search JIRA for a development request. I suspect that you won't find one.

I might add one then :-)