Re: [ZODB-Dev] RelStorage and PosKey errors - is this a risky hotfix?
On 02/02/2011 09:14, Shane Hathaway wrote: > On 02/02/2011 10:57 AM, Chris Withers wrote: >> Er, since when? If that were the case, I'm sure Shane would place >> explicit instructions that it should not be used... > > Safe is relative. MySQL is a good choice for Facebook, but if I knew my > bank was storing my account balance in MySQL, I would close my accounts > immediately. I'll have to respectfully disagree... MySQL has come a long way over the last 10 years, and I'm as confident in it as I am in any relational database, particularly when used with the InnoDB engine. cheers, 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
Re: [ZODB-Dev] RelStorage and PosKey errors - is this a risky hotfix?
On 02/02/2011 10:57 AM, Chris Withers wrote: > Er, since when? If that were the case, I'm sure Shane would place > explicit instructions that it should not be used... Safe is relative. MySQL is a good choice for Facebook, but if I knew my bank was storing my account balance in MySQL, I would close my accounts immediately. 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 and PosKey errors - is this a risky hotfix?
On 01/02/2011 23:10, Ruda Porto Filgueiras wrote: > I had similar issues on past and now I follow some rules: > > - pack only with zodbpack > - pack-gc = false ...which means your database will still slowly (or quickly in my case!) grow over time with unreferenced objects. > - pack when the database is not been active update or not update at all. I'm glad you have an app with quiet spells! ;-) This isn't realistic for any active, public web app. > But it does not imply RelStorage bug, since MySQL is know to not be so "safe". Er, since when? If that were the case, I'm sure Shane would place explicit instructions that it should not be used... cheers, 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
Re: [ZODB-Dev] RelStorage and MySQL wait-timeout
On 01/02/2011 18:11, Shane Hathaway wrote: > On 02/01/2011 07:51 PM, Chris Withers wrote: >> I can understand the problem being fairly terminal if there was a >> disconnect *during* a timeout, and I'd expect an exception, but not a >> segfault ;-) > > I haven't seen segfaults except when the dynamic linker used an > incorrect library. Use "ldd" to check the .so files generated during > buildout. Surely these would occur all the time? I've only seen them occur on two occasions, and the same buildouts have worked fine the rest of the time... cheers, 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
