Re: [ZODB-Dev] Default comparison considered harmful in BTrees.
Or perhaps make it emit DeprecationWarnings, but continue working. Then make it a fatal error in the next minor/major release. +1 Pedro -- José Pedro Ferreira Indico Team IT-UDS-AVC 513-R-0042 CERN, Geneva, Switzerland ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
Re: [ZODB-Dev] Default comparison considered harmful in BTrees.
On 25/10/2010 23:34, Marius Gedminas wrote: Or perhaps make it emit DeprecationWarnings, but continue working. Then make it a fatal error in the next minor/major release. Well, not a DeprecationWarning... Is there a DataLossWarning? Still, +1 on the warning followed by exception in 2 releases... Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
[ZODB-Dev] RelStorage: Write on master, read from slave(s)?
Hi, In order to scale an application using RelStorage I was thinking about seperating reads and writes accross databases. Writes would go to a Mysql master and the app would read from one or more Mysql slaves. It looks like RelStorage already keeps seperate connections for read and write (even though they are not exposed through configuration), so it is probably easy to set up. Would it work or is there a risk of getting inconsistent data? Or is that entirely up to the ability of doing synchronous replication of the underlying database? /Anton ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
Re: [ZODB-Dev] RelStorage: Write on master, read from slave(s)?
On 10/26/2010 04:04 AM, Anton Stonor wrote: In order to scale an application using RelStorage I was thinking about seperating reads and writes accross databases. Writes would go to a Mysql master and the app would read from one or more Mysql slaves. If you mean that you intend to set up some clients to write to a master database, while other clients only read from asynchronous replicas, then yes, you'll be in good shape. You should be able to get amazing scalability that way. It looks like RelStorage already keeps seperate connections for read and write (even though they are not exposed through configuration), so it is probably easy to set up. Would it work or is there a risk of getting inconsistent data? Or is that entirely up to the ability of doing synchronous replication of the underlying database? These questions make me wonder if you're thinking of something more complicated than the plan I described above. Shane ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
Re: [ZODB-Dev] RelStorage: Write on master, read from slave(s)?
Hi Shane, In order to scale an application using RelStorage I was thinking about seperating reads and writes accross databases. Writes would go to a Mysql master and the app would read from one or more Mysql slaves. If you mean that you intend to set up some clients to write to a master database, while other clients only read from asynchronous replicas, then yes, you'll be in good shape. You should be able to get amazing scalability that way. That is what I want. Sounds great. My assumption was that if a client was reading from a relica before fresh data was replicated I would get old data. That was why I was talking about synchronous replication. /Anton ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
Re: [ZODB-Dev] Default comparison considered harmful in BTrees.
On Mon, Oct 25, 2010 at 6:34 PM, Marius Gedminas mar...@gedmin.as wrote: ... Or perhaps make it emit DeprecationWarnings, but continue working. Then make it a fatal error in the next minor/major release. I like this idea. I think I'm going to use UserWarning because it isn't disabled in Python 2.7 afaik. Otherwise, I would liie deprecation warning because it suggest that things are bad and going to get worse. :) Jim -- Jim Fulton ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev