[db-wg] Database release 1.79.1 deployed to RC environment

On Thu, May 07, 2015 at 09:55:25AM +0200, Tim Bruijnzeels wrote:

Dear WG Members

> > On 06 May 2015, at 18:14, denis <ripedenis at yahoo.co.uk> wrote:
> > 
> >> If an object is submitted without any changes it will always result in an update, because when we compare the object the "last-modified:" value will typically not match.(unless the update is done at sub-second speed) In other words what should be a "no-op" now results in a "touch" operation where only the "last-modified:" attribute is changed.
> > 
> > Just an observation. This might actually be a useful side effect. It allows maintainers of objects to 'touch' their objects and show they are alive and actively maintaining their data even when nothing needs to change. I am sure some people in the community who are going to start monitoring "last-changed:" attributes to argue that data is out of date would appreciate that, or even request it.
> 
> Sure, there is something to be said for this, but the downside of this
> is that the version history of the object becomes very large, which
> may not be desired.

And the purpose of having such history is quite unclear.

> As far as I know this was not explicitly specified beforehand, so it
> would be good to have a clear WG consensus call on this now.

+1

> For the moment we feel that it's probably best to apply the planned
> 'fix' because the behaviour will then be consistent with no-ops until
> now, but we can always revert this change when we get a clear
> direction from the WG.

+1

Piotr

-- 
gucio -> Piotr Strzyżewski
E-mail: Piotr.Strzyzewski at polsl.pl