Hello,
We're currently deploying plone with zrs which replicates to read-only
databases which is what actually gets served to the user. It works
fine in most cases, but there seem to be odd issues here and there
where plone will try to write to the database and will throw an error
on the page
On 9/27/10 9:48 AM, Nathan Van Gheem wrote:
Hello,
We're currently deploying plone with zrs which replicates to read-only
databases which is what actually gets served to the user. It works
fine in most cases, but there seem to be odd issues here and there
where plone will try to write to
For anyone who cares. ZODB trunk builds win32 and amd64 have been
passing tests for almost a week without failures. Thanks Jim for
getting ZODB tests working reliably on Windows!
cheers
alan
p.s. let us know if you need py2.7 builders and what to test. you can
find all the builders at
Can you rephrase that with fewer nots? I'm not quite sure what you're
asking...
:) Yes. We would like our read-only zodb to still serve pages even if
plone tries to write to the database. Basically, we'd like to suppress
the read-only errors you get when you try to write to a read-only
BTW, I thought I could just use the ZPublisherEventsBackup to abort
every transaction when zope is in read-only... Kind of hacky, but not
too bad :)
On Mon, Sep 27, 2010 at 12:24 PM, Nathan Van Gheem vangh...@gmail.com wrote:
Can you rephrase that with fewer nots? I'm not quite sure what you're
On 27 September 2010 18:26, Nathan Van Gheem vangh...@gmail.com wrote:
BTW, I thought I could just use the ZPublisherEventsBackup to abort
every transaction when zope is in read-only... Kind of hacky, but not
too bad :)
That sounds really evil, but I guess it should work...
plone.app.imaging
p.s. let us know if you need py2.7 builders and what to test. you can
find all the builders at hudson.enfoldsystems.com
tests are passing on py2.7 as well.
https://hudson.enfoldsystems.com/view/Zope/
___
For more information about ZODB, see the
