I agree that it's handy, and that people would be upset if it
disappeared. But I also agree that people trust it far more than they
should, and that it's really only dependable for developers to roll
back transactions -- however, for that, I think it's invaluable (i.e.
very valuable).
So I think
On 24/12/09 03:09, Martin Aspeli wrote:
Hanno Schlichting wrote:
Unfortunately, I think the people most likely to have used it in a pinch
are less likely to be reading this list.
If the current API is broken, we should fix it. If that means fixing
some of the UI in Zope to use a new API,
On Wednesday 23 December 2009 20:26:13 Jim Fulton wrote:
Undo is broken in a number of ways. Does anyone care? Does anyone use
undo?
First, a disclaimer: what I state below is from Zope 2.8-ish experiences, with
its original ZODB version. I hope my mail is still on topic nevertheless.
In my
I'm looking at undo today because it is complicating ZEO transaction management.
Undo is broken in a number of ways. Does anyone care? Does anyone use undo?
Undo is broken in the following ways:
- The TransactionalUndo resource manager invalidates objects too early.
- If undo is mixed with
We use undo from time to time in a zeo setup. When it works it can be
a life saver! :) If it goes away I guess it wouldn't be the end of
the world though.
-EAD
Erik A. Dahl
Co-Founder and CTO, Zenoss Inc.
phone: 443-837-2597
http://www.zenoss.com
On Dec 23, 2009, at 3:26 PM, Jim
On Wed, Dec 23, 2009 at 3:38 PM, Erik Dahl ed...@zenoss.com wrote:
We use undo from time to time in a zeo setup. When it works it can be a
life saver! :) If it goes away I guess it wouldn't be the end of the world
though.
Do you use it via Zope 2 or do you call ZODB undo apis directly?
Jim
Zope 2.
-EAD
Erik A. Dahl
Co-Founder and CTO, Zenoss Inc.
phone: 443-837-2597
http://www.zenoss.com
On Dec 23, 2009, at 3:40 PM, Jim Fulton wrote:
On Wed, Dec 23, 2009 at 3:38 PM, Erik Dahl ed...@zenoss.com wrote:
We use undo from time to time in a zeo setup. When it works it can
be
On Wed, Dec 23, 2009 at 9:26 PM, Jim Fulton j...@zope.com wrote:
Undo is broken in a number of ways. Does anyone care? Does anyone use undo?
Speaking from the Zope2/Plone crowd: I'm using it during development
with a local file storage at times.
In a real ZEO production setup, undo in Plone
On Dec 23, 2009, at 2:26 PM, Jim Fulton wrote:
On Wed, Dec 23, 2009 at 4:20 PM, Jeff Shell j...@bottlerocket.net wrote:
Are you asking at the ZODB level, or at a higher level, such as Zope?
I'm asking if applications are using undo these days.
We use it in our Zope 3 based CMS. We
Jim Fulton wrote:
So, I repeat: is anyone actually using undo these days?
I haven't used undo (not the APIs nor via any Zope UI) in years.
- C
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing
Jim Fulton wrote:
I'm looking at undo today because it is complicating ZEO transaction
management.
Undo is broken in a number of ways. Does anyone care? Does anyone use undo?
Plone users tend to use Undo quite a lot. If you accidentally delete
something, say, it's pretty much your only way
Hanno Schlichting wrote:
On Wed, Dec 23, 2009 at 9:26 PM, Jim Fultonj...@zope.com wrote:
Undo is broken in a number of ways. Does anyone care? Does anyone use undo?
Speaking from the Zope2/Plone crowd: I'm using it during development
with a local file storage at times.
In a real ZEO
On Thu, Dec 24, 2009 at 1:34 AM, Martin Aspeli optilude+li...@gmail.com wrote:
Hanno Schlichting wrote:
Throwing away all changes done in the meantime is usually
not practical.
... although sometimes it is preferable to a full backup restore or
living with whatever it is you want to restore
Hanno Schlichting wrote:
What is zc.beforestorage?
Look at its PyPi page http://pypi.python.org/pypi/zc.beforestorage
Thanks for the pointer!
In practice it hardly ever works. Relying on it as a substitution for
backup or tested restore procedures is dangerous.
I know that a procedure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
Hanno Schlichting wrote:
What is zc.beforestorage?
Look at its PyPi page
http://pypi.python.org/pypi/zc.beforestorage
Thanks for the pointer!
There is also dm.historical when you need to deal with earlier versions
of
I'd like to add my vote to retaining Undo, I think it's a crucial
feature. Changing the API is not a problem, and changing the UI could
probably be an improvement. I use it all the time, especially when
fiddling with customer datatabases for upgrades or bugfixes.
--
Lennart Regebro:
16 matches
Mail list logo
