There are 2 potential avenues for providing this functionality.
1) When we re-implement generations, it may be possible to query this kind of model evolution or;
2) We are looking at implementing status-history as tagged logging and *not* in the database. It makes sense to enable this scenario in such a solution.
There are 2 potential avenues for providing this functionality.
1) When we re-implement generations, it may be possible to query this kind of model evolution or;
2) We are looking at implementing status-history as tagged logging and *not* in the database. It makes sense to enable this scenario in such a solution.