Dieter Maurer wrote:
Let a bug occur in some component and then, instead (or in addition)
of fixing the bug, we say often: rip the component off Zope.
That was threadened for Versions, and ZClasses and now
for Refresh.
Well, they all don't work right, confuse people are aren't
Tim Peters wrote at 2005-7-15 16:06 -0400:
...
Anyway, for reasons explained before, making a savepoint would still need to
copy the index, so I don't see that this would save anything worth saving.
It might allow skipping an index copy when a _rollback_ is done (at the cost
of clumsier coding
On Sat, 2005-07-16 at 12:00 -0400, [EMAIL PROTECTED] wrote:
|
| But otherwise, refresh saved me *lots* of time...
Same here. If you know the gotchas and you program properly it can
work flawleslly. Hell, I've even been able to refresh Archetypes
products, what can be more prone to fail
