I\'m working in a case require fairy complex use of page views.
Each content object will have page view, and this should be accessed easily so that we can do various
A write on every access is a worst-case scenario for the ZODB. Relational DBs are generally pretty good at this sort of thing, and I'd look at that first.
Need to sort on the data? Just add some utility or content type methods to query the db. When you need to lookup, do the catalog search, then use the db-connecting methods to annotate the data for the sort.