| I started work on a implementing the changes I proposed here: https://gist.github.com/sebersole/2c9ad6b77ea3477ba508c21c6ab61b8d There is one design question discussed in HipChat and carried over into the comments there. For most part the design changes were pretty smooth to integrate in hibernate-core. I did unearth a new design question though.. basically how to translate QueryResultsRegion and TimestampsRegion into this new paradigm. There are 2 options I see (aside from different "tweaking" from the start):
- Have 2 distinct types of region correlated more or less to what used to be TransactionalDataRegion and GeneralDataRegion. While it may make sense to allow mixing entity and collection data in a single region, it never makes sense to allow entity and/or collection data to be mixed with query-result data and/or update-timestamps data. So in that sense, having the 2 distinct Region types makes some sense.
- Have a new "access strategy" for QueryResultsRegion and TimestampsRegion (GeneralDataRegion).
|