The use case is that the user requires a specific index implementation which is either totally outside the store or stored in a Singleton and when they update a table, they also maintain the index. It would be nice to be able to do provide help in doing this so that the code can execute as part of the transaction, changes are supplied in convenient form, and/or some other way to make maintaining the index easier.
Some possible solutions: having a commit_with method which takes a function which operates on the transaction's change set and is executed between the commit check and the actual commit, or custom indexes where the user supplies the index implementation.
The use case is that the user requires a specific index implementation which is either totally outside the store or stored in a Singleton and when they update a table, they also maintain the index. It would be nice to be able to do provide help in doing this so that the code can execute as part of the transaction, changes are supplied in convenient form, and/or some other way to make maintaining the index easier.
Some possible solutions: having a
commit_withmethod which takes a function which operates on the transaction's change set and is executed between the commit check and the actual commit, or custom indexes where the user supplies the index implementation.