Hey Drizzle folks... I met with Brian and other day and he got me sufficiently interested in Drizzle that I'm here now. :-)
For reasons that continue to mystify me, launchpad is not sending me group emails yet. Luckily, I can read via the web archive. Ping me off-list if you have any clues on that. Anyway, we talked a bit about the replication protocol and possibly moving to something more flexible like protocol buffers[1] or Thirft[2]. That'd be handy, since I've occasionally had a desire in the past to whip up a Perl client that can speak MySQL replication. But then today we had a network glitch at work[3] that caused a corrupted log entry to get written to the slave's relay log. THAT SHOULD NEVER HAPPEN. There should be a simple checksum (CRC, MD5, whatever) on the log event that the slave can check before committing it to disk and expecting the SQL thread to be able to parse it. Fixing that by hand wastes my time, and I really don't like things that waste my time. So consider this a feature request. If the protocol is going to change anyway, let's make sure this 5+ years of FAIL does not continue. Oh, and since I haven't already said so, I'm really happy to see this effort underway... Thanks, Jeremy [1] http://code.google.com/p/protobuf/ [2] http://incubator.apache.org/thrift/ [3] http://craigslist.org/
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
