best use comprehend long-term history-mode o/rm system(hibernate)?
i have mapped several java classes customer, assessment, rating, ... database hibernate.
now i am pondering history-mode changes determined data. concentration web application. box deletion (or editing) information another user should have luck changes mislay it. given changes out range tide session, i don't know solve something management pattern, permitted mislay functionality.
for unparalleled value modifying an proceed sounds ok. nonetheless deletion whole determined entity? simplest proceed emanate fall list fan deleted not. complexest proceed emanate list any category where deleted entities stored. there anything between? i combine twin things o/rm component (in box hibernate) comfortably, but messing around many sql (which i wish prevaricate since portability) still have adequate flexibility?
is there best practice?
Comments
Post a Comment