From: https://groups.google.com/forum/#!topic/google-mysql-tools/Bc7P5SIRCVE/discussion
<https://groups.google.com/forum/#!topic/google-mysql-tools/Bc7P5SIRCVE/discussion>[This message is being sent to the google-mysql-tools Google group, which has been inactive for a very long time. If you no longer wish to receive these messages, please unsubscribe at googlegroups.com] I'm happy to announce a new round of Google MySQL tool releases. We're just getting started, but here's what's available so far: - db.py<http://code.google.com/p/google-mysql-tools/source/browse/trunk/pylib/db.py>: Easily execute queries in parallel on a sharded database - sql.py<http://code.google.com/p/google-mysql-tools/source/browse/trunk/sql.py>: Interactive shell to db.py - permissions.py<http://code.google.com/p/google-mysql-tools/source/browse/trunk/permissions.py>: Manage MySQL permissions in a Python-based format - validate.py<http://code.google.com/p/google-mysql-tools/source/browse/trunk/validate.py>: Parse SQL using pyparsing and apply rules with live DB data These are the actual tools being used to run MySQL at scale inside Google, not one-time sanitized copies. You can get them at http://code.google.com/p/google-mysql-tools/. The old tools and patches are still available in old/<http://code.google.com/p/google-mysql-tools/source/browse/#svn%2Ftrunk%2Fold> . Thanks to the whole team for their work on these tools and especially to Razvan Musaloiu-E. for handling release code reviews. If you'll be at the 2011 MySQL conference <http://en.oreilly.com/mysql2011/>, stop by my talk with Eric Rollins <http://en.oreilly.com/mysql2011/public/schedule/speaker/8129> on automatic failover <http://en.oreilly.com/mysql2011/public/schedule/detail/17137> and Mikey Dickerson <http://en.oreilly.com/mysql2011/public/schedule/speaker/57828>'s on detecting data drift<http://en.oreilly.com/mysql2011/public/schedule/detail/17138> . On Fri, Apr 1, 2011 at 3:49 PM, howesc <how...@umich.edu> wrote: > haven't seen any news either. it's probably an indication that they are at > least testing it. > > cfh > -- Imagine there were no hypothetical situations.
