Hi,
Sinang, Danny wrote:
Hello,
We've got lots of Catalog reads and writes and our Data.fs is growing
at an immense rate.
Is there a way we can tell Zope to stop storing old object
versions to limit the growth and not have to pack that often ?
Well in fact it (Filestorage) does only "st
Sinang, Danny wrote:
Hello,
We've got lots of Catalog reads and writes and our Data.fs is growing
at an immense rate.
Is there a way we can tell Zope to stop storing old object
versions to limit the growth and not have to pack that often ?
Well in fact it (Filestorage) does only "store" new ob
- Original Message -
From: "Sinang, Danny" <[EMAIL PROTECTED]>
To: "Jonathan" <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, May 08, 2008 10:03 AM
Subject: RE: [Zope] Making Zope stop storing old object versions
How do I go about replacing a Catalog usin
g. So we either rewrite it to use MySQL, or we find a way to make
Catalogs write to MySQL.
Regards,
Danny
-Original Message-
From: Jonathan [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 08, 2008 10:08 PM
To: Sinang, Danny
Cc: zope@zope.org
Subject: Re: [Zope] Making Zope stop storing old
How do I go about replacing a Catalog using MySQL ? This is the first
time I've heard this.
-Original Message-
From: Jonathan [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 08, 2008 7:16 PM
To: Sinang, Danny
Cc: zope@zope.org
Subject: Re: [Zope] Making Zope stop storing old o
(Thu, May 08, 2008 at 08:08:28AM +0800) Sinang, Danny
wrote/schrieb/egrapse:
> We've got lots of Catalog reads and writes and our Data.fs is growing
> at an immense rate.
Sometimes you have to look at your product code and figure out what it's
exactly doing. For example many times not very optimal
Hi,
Jonathan wrote:
Sinang, Danny wrote:
Hello,
...
You can also try some of the other storages like relstorage (where it
depends on the RDBMS how it handles writes)
Alternatively, you could just replace your Catalog with an external db
such as MySQL (using zmysql database connections).
w
