![]() ![]() Work / complexity as changes need to also be reflected in associated history tables and triggers. ![]() ![]() (on more base tables) than the traditional trigger based approach.Ī downside to relative to using Change log is that schema changes (like adding a column) can mean more Into the history tables in the background and in batch and that probably means it can generally be used more widely The approach with Oracle Total Recall reduces the impact to response time by processing the copy of data from redo Now also copy data into the history tables. Of storage (history tables taking storage space) and in terms of impact to response time as updates and deletes Into say ElasticSearch and creating appropriate queries to return as of and version type data).Ī downside to relative to using Change log is that it does introduce extra costs to the database in terms This is also possible with Change log but requires more work (loading the change log With it is easy to query and view the data "As of" a given timestamp and view the versions and historicĬhanges for a given bean/row. Although Ebean makes itĮasier to query and generate the appropriate DDL the capturing of changes is a database function and not strictly Is used to update the database all these changes are captured by the database triggers. If other frameworks (not Ebean) or stored procedures or raw JDBC With changes are transactional and have the associated guarantees - changes can't be missed or lost.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |