| « Changes of Visibility | Free on Rollback » |
Local View of Data
April 5th, 2007
One could do this, add a flag to the perminant index that says whether it is inserted or deleted, and has a version number, and then, when building the histories, one determines if, that has changed.
Also, their is a new thought, where those things do not change until absolutely necessary, which means, that, you’d create a view of the database, by building a mutation specific index, changing that mutation specific index, and then merging with the common to see what’s what.
The final commit would be as it is now in Memento, lock everything, make sure it has not changed. One could have a difference between row level locking and table level locking.
Table level, because we may need to lock the entire table, when things change significantly. If a join is rejiggered or some such.
The mutator’s view could be stored in standard Java containers, or in the future, it could be logged, or kept in a lazy index, one that writes out only when memory is needed.
comment
One Response |
One could do this, add a flag to the perminant index that says whether it is inserted or deleted, and has a version number, and then, when building the histories, one determines if, that has changed.
Also, their is a new thought, where those things do not change until absolutely necessary, which means, that, you’d create a view of the database, by building a mutation specific index, changing that mutation specific index, and then merging with the common to see what’s what.
The final commit would be as it is now in Memento, lock everything, make sure it has not changed. One could have a difference between row level locking and table level locking.
Table level, because we may need to lock the entire table, when things change significantly. If a join is rejiggered or some such.
The mutator’s view could be stored in standard Java containers, or in the future, it could be logged, or kept in a lazy index, one that writes out only when memory is needed.