5 Replies Latest reply on Sep 17, 2002 11:11 AM by Kelly MacInnis

    Dirty data -- the bean is not always king

    Kelly MacInnis Newbie

      Here is the problem,

      The database has points of contact other than any given bean, scheduled jobs can change data, triggers in the database can modify data while it is stored, and another user's bean can change stuff. The bean loads the data and thinks that it is the only one that can touch it. I have a way to tell that the data is dirty when storing but by then it is too late. Some process thought everything was fine and went on and now the data can’t be stored. There is also a chance that the data was changed by another process after the load and it is already dirty before anything is even served up to the client.

      Is there a way to get the container to check and see if the data is dirty and re load it or force the container to always do a load?