> > possible to make an object immutable... for instance, I've got a country > > list and the data doesn't change, and I want to make sure that one of my > > developers can't alter the table (particularly in the production env). > > Currently in my own design I'm using a fairly simple JavaBean system, and a > > factory behind the beans... this allows the factory to throw a veto > > exception if the data is immutable and someone tried to change it. Does > > anything like that exist in this API? > > Not on the API level. Access rights should be addressed on the DB level > (with grants).
In this case, using separate users for each object that needs r/w or read only would be seriously messy. I should be able (in the object mapping) to set an immutable parameter to the system know that new existing objects can be changed. You could even extend this further with a set of "permissions" as in "allow select: disallow update, create, delete" IMO this is object level permissions, not DB permissions really, because the OBJ-DB layer still has to be able to manipulate the DB under its account (it's also much more expensive to use grant). Another related ability, is a locking ability... a kind of weak lock. so that objects did not get updated unless they where specifically "enabled" for update... I'm thinking that could be put into the object layer easily though. - Brill Pappin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
