On 27 September 2010 18:26, Nathan Van Gheem 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 / plone.scale cr
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 wrote:
>> Can you rephrase that with fewer "not"s? I'm not quite sure what you're
>> asking...
>
> Can you rephrase that with fewer "not"s? 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
datab
> 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 lo
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
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 load
