is it a good practice to make use of

automatic dirty checkig concept in application programming?

Hi,
This is my view.
On the brighter side ( using Automatic Dirty Checking )
i) We rely on somebody else to persist the changes made by us without really being concerned with,
a) when to do it ?
b) how to do it ? ( selectively update columns etc. )
ii) The Less we Code, Lesser are the Bugs introduced. So, its handy to use a tried and tested utility.
iii) Automatic Dirty Checking units ( like the one in Hibernate , findDirty() ) are flexible to an extent that we can provide custom routines to determine if objects are dirty.

On the Darker side,
i) We have a dependency on this unit. Yes a dependency. ( If not, my application would handle this logic )
ii) At times this feature can be irritating. ( we are forced to remove the object to detached state, if we intend to modify the object with no intentions of persisting it. But, again this is not a good practice.


------------------------------------------
Rate the reply if you find it helpful