This is not a an April's Fool but I cannot say much more yet.
On Apr 2, 4:03 pm, Carl <m...@carlroach.com> wrote: > As you're replying to this on April 2nd I guess it's not an AFool :) > > Excellent news for the Web2py platform; I look forward to the full > story in due course. > > On Apr 2, 4:47 pm, Massimo Di Pierro <massimo.dipie...@gmail.com> > wrote: > > > > > > > > > I guess this partially releases me from the Non Disclosure Agreement. > > > I have been testing this since December under contract with Google. > > I have a web2py version that runs on GAE with MySQL. > > It supports MySQL and the Datastore at the same time. > > Automatic migrations work too. > > > I will release it as soon as I get permission to do so. > > > Massimo > > > On Apr 1, 6:44 pm, Shishir Ramam <sra...@gmail.com> wrote: > > > > From:https://groups.google.com/forum/#!topic/google-mysql-tools/Bc7P5SIRCV... > > > > <https://groups.google.com/forum/#!topic/google-mysql-tools/Bc7P5SIRCV...>[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...>: > > > 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/permi...>: > > > Manage MySQL permissions in a Python-based format > > > - > > > validate.py<http://code.google.com/p/google-mysql-tools/source/browse/trunk/valid...>: > > > 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 > > > athttp://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%2Ftrun...> > > > . > > > > 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.
