[EMAIL PROTECTED] wrote at 2008-7-31 15:09 -0400:
> ...
>> I don't have experience with running the db in readonly mode in
>> production.
There is no difference in cache handling between readonly and readwrite
mode.
An old thread explains why this (no-difference) is necessary.
--
Dieter
Gary Poster <[EMAIL PROTECTED]> wrote on 07/31/2008 01:07:39 PM:
> I'm the primary zc.catalog author.
>
> He is running read-only, so savepoints shouldn't be very pertinent.
>
> The original poster is correct that the cache is cleaned out at
> transaction boundaries (or savepoints, as Alan said
[EMAIL PROTECTED] wrote on 07/31/2008 11:55:38 AM:
> I believe it is common to have a theshold (say every 1) objects to
> do a savepoint
> and then you can run cacheMinimize after the savepoint.
>
> surprised the zc.catalog does not provide this sort of knob. maybe it
> was a problem
> in the
I'm the primary zc.catalog author.
He is running read-only, so savepoints shouldn't be very pertinent.
The original poster is correct that the cache is cleaned out at
transaction boundaries (or savepoints, as Alan said).
I don't have experience with running the db in readonly mode in
produ
I believe it is common to have a theshold (say every 1) objects to
do a savepoint
and then you can run cacheMinimize after the savepoint.
surprised the zc.catalog does not provide this sort of knob. maybe it
was a problem
in the original ZCatalog implementation?
cheers
alan
On Wed, Jul 30, 2
