Hey
Awhile back the subject of tuned dbms updates arose, and a couple of
vendors claimed to support it.
I am interested in hearing how this is accomplished.
My suspicion of the claims comes from the following. I can see these
implementation possibilities:
1. upon ejbLoad store the fresh values. When ejbStore is called simply
compare the stored values with the current, and store the modified ones.
2. Postcompile the EntityBean classes so that all operations which set
the value marks the field as dirty. ejbStore then only stores the dirty
fields, if any.
1. relies on the correct implementation of equals() in all objects. Can
this be guaranteed, especially for complex objects?
2. fails if an attribute is mutable, in which case it is possible to
change the value of the field without actually settig it.
Are there any more implementation possibilities?
If any of the above are used, how are the given problems handled?
Thanks!
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
