On Thu, May 3, 2012 at 1:49 AM, Stanislav Muhametsin <[email protected]> wrote: > I think this is a step in the correct direction. But I am not sure if > there will be found API satisfying all possible entitystores.
I think by keeping the Entity Store SPI relatively simple, custom implementations should be within reach for any significant project. > Like, > should there be a way for end-users to customize how history is stored > (separate file/table or some other way), should there be there any > additional information than just timestamp (and could that be customized > as well?), etc. Yes, that is an important question. One possible solution is that we leverage/extend the "usecase" concept, allowing for better extension of the basic one (just a name), store each usecase and associate every transition back to the usecase. That would then not require any timestamp on actual Property, as it could be a shared TS on the usecase. That allows for instance stronger audits to be built. Another area that needs to be analyzed is Indexing/Query. Since the Query is executed against a UnitOfWork, the Indexing system should also support the "asOf" attribute in the UoW. This will probably make Indexing even harder than currently. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/3xugrbk I work here; http://tinyurl.com/6a2pl4j I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
