Hi Shane,
Well, it's already in the docs. Look for "1.2.1" in README.txt.
Doh - I was too fast.
I'll accept suggestions on how to reorganize the documentation to make
this more noticeable.
Well, it's actually quite clear as is, I realize. But a trouble shooting
section possible including
Wichert Akkerman wrote:
For some of us a the main reason for using RelStorage is to be able to
satisfy the 'all data must be stored in our oracle cluster' requirement
from enterprise customers. That means we can not use NFS mounts to store
blobs.
You have a point, and I know how stubborn ente
Anton Stonor wrote:
Just wanted to share that RelStorage does not work with the MySQLdb
1.2.1 adapter. 1.2.2 seems to work fine. [...] Maybe this requirement
could go into the docs?
Well, it's already in the docs. Look for "1.2.1" in README.txt.
http://svn.zope.org/relstorage/tags/1.0/README
Hi there,
Just wanted to share that RelStorage does not work with the MySQLdb
1.2.1 adapter. 1.2.2 seems to work fine.
The symptom is this error message while starting up Zope:
cPickle.UnpicklingError: unpickling stack underflow
The reason is that MySQLdb 1.2.1 tampers with the pickles whi
On Wed, May 07, 2008 at 08:33:34AM -0300, David Pratt wrote:
> Hi Christian. Curious, what were you using for postgres replication?
> Many thanks.
The only solution that I know of is slony (which is also sold in a commerical
wrapping by EnterpriseDB) which is very awkward. I'm not aware of other
Hi Christian. Curious, what were you using for postgres replication?
Many thanks.
David
Christian Theune wrote:
I'm kind of curious what a match of RelStorage and ZEORaid may give. FWIW my
experiences with Postgresql replication aren't that good so you could still go
that route using two Rel
