Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[] [Bug 249745] Eclipse Repository Best Practices  
Product/Component: Community / Architecture Council

--- Comment #7 from Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>  2008-10-06 13:55:08 -0400 ---
(In reply to comment #6)
> Aw come on, Gunnar, that's pushing it. MySQL and Oracle provide tools for
> admins to delete, modify and move data.

That's the point, they provide tools you *have* to use.

> You can bet that if I had to dump a
> database to a text file, edit it, then re-import it just to delete a row, I
> wouldn't be in IT.

Frankly, on some databases that's necessary to guarantee the nuclear launch
codes are really gone.

> It's the sysadmin's job to enforce data integrity with the tools at their
> disposal (either through the database or otherwise) and according to their
> rules, not the self-righteous SVN developers who think it must be so.

Yes, thats' indeed a problem. Unfortunately, all the other SCMs mentioned here
do require the same sort of dump/filer/load/compact cycle to really remove the
bits. That's the point I was trying to make. A new SCM won't really help the

If you've already pushed your changes to a public repository that people have
cloned from, the genie is out of the bottle. Good luck cleaning up your mess.

Similar answers are given for Git and Bazaar.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

Back to the top