Re: A few dumb questions

[Brandon Goodin]

I guess I don't see how what you are saying solves the problem I am stating.   1) I send a sql statement to the database it returns a resultset 2) The resultset is iterated and keys are examined to see if the objects exist in the application object layer already. 3) If the object does not exists it is created and added to the object layer. If the object does exist it is not created and the object in the object layer is left alone 4) I get a copy of the object from the object layer 5) I make changes to my copy of the object 6) My persistence solution examines my object against the object in object layer and updates the database with a crafted update statement. 7) database and object are in sync   Question:   So, looking at step 3 how does the persistence solution know that the record in the database is the same when the object in the object layer has been retrieved already and another completely different application altered its related record in the database?     I guess you could MD5 every record and compare it to a stored key for each object to examine for changes against the related record. I prefer to use the database.   Do you get what I am saying? Anyone else understand what I am saying? Am I missing a brilliant point from Oliver?   Feeling insecure ;-) Brandon