[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: the obliterate discussion - why dumpfiltering is no valid workaround

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: 2007-07-20 22:31:57 CEST

Karl Fogel wrote:
> Les Mikesell <lesmikesell@gmail.com> writes:
>> Erik Huelsmann wrote:
>>> I work in a financial institution. Users make mistakes. We correct
>>> them, but the original error stays in the database, forever.
>> What would you do if a user included something in your database that
>> would be illegal for you to store or redistribute to anyone else? And
>> I doubt if your comparison really comparable in other respects. Can a
>> user accidentally include a DVD image in a database update instead of
>> a small change?
> I think you might be misunderstanding Erik's point.
> He's not arguing that it's okay for errors to stay in the database
> forever. He's saying that users make mistakes, and that even though
> they can correct those mistakes for the future, the original mistake
> stays around forever, and that's a *bad* thing. He's on your side :-).
> (As am I.)

I took it the other way. Financial transactions need a real audit trail
so there's a good argument for saying that mistakes and their
corrections should be tracked forever. But that situation doesn't have
much in common with an open-ended storage system like subversion where
what goes/stays should be entirely based on local policy and not forced
by technical difficulty.

   Les Mikesell
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 20 22:49:14 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.