Am Donnerstag, den 22.03.2007, 15:00 +0000 schrieb Chris Withers: > Benji York wrote: > >> Nah, the changes need to be permenant, tested, and then rolled back... > > > > I can't reconcile "permanent" > > ie: committed to disk, not DemoStorage... > > > and "rolled back". :) > > undo the changes committed to disk, to a point in time, once the results > have been tested. > > > If the app needs to be restarted and the changes need to remain intact, > > you could connect to the demostorage via zeo and then app restarts would > > leave the demostorage intact. Then when you want a roll back you can > > restart the zeo server. > > DemoStorage keeps all its data in memory, right? In which case, even if > this were a good idea, the machine will not have enough memory to keep > the changes being made...
Virtual memory to the rescue? :) -- gocept gmbh & co. kg - forsterstraße 29 - 06112 halle/saale - germany www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 - fax +49 345 122 9889 1 - zope and plone consulting and development
Description: Dies ist ein digital signierter Nachrichtenteil
_______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev