Re: [xwiki-devs] Suport for non versioned properties and more efficient saving

Yes.. The use case is to use this for storing information that is related to a wiki page but that at the same time can be update many many times and if we do it would create a huge amount of version and impact performance. Not being able to rollback would be a known behavior and this would be used for data that we are not interested in history of and that many times we could recalculate. In many cases it could be to store aggregate information that would be faster to access. Example: - last connection time of a user : it is only available using an aggregate query and could be costly to access if you wanted to show this next to each user. With a non versioned property you would have this in the user document cache. - last update time of a feed in XWiki Watch and number of articles loaded (currently this generates tons of versions of the document and forces us to clear versions, thus potentially loosing important history information) - average page rating or user rating (this is a requirement of the Socracy project http://www.socracy.org) calculated after each rating. - watch list adding a page to watch for a user (not sure if this one would be a use case as we might want the rollback for this) These non versioned property could be updated using Groovy Notifications or could be updated using Groovy Scheduler Jobs.. The other requirement is about being more efficient when saving which also would allow XWiki to be more efficient for application with many saves on big documents with many objects and properties. Ludovic Vincent Massol wrote: -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost