List:Internals« Previous MessageNext Message »
From:Davi Arnaut Date:December 17 2012 5:14am
Subject:Re: Envisaged Binary Log Changes
View as plain text  
On Sun, Dec 16, 2012 at 4:05 PM, Stewart Smith <stewart@stripped> wrote:
> 5.6 introduces some decent changes, and it's likely that the same kind
> of features may be implemented slightly differently in MariaDB (maybe
> Monty or Kristian can comment more).

For what it's worth, changes in the binary log format are usually
backwards compatible in the sense that certain (e.g. new) events can
be skipped if need be.

> The binlog itself is notoriously hard to parse, although the Oracle guys
> did get out an API (although not marked as stable, it should be rather
> usable). The binlog was never really meant to be a point for other
> software to interface with MySQL and so like any software, when you
> delve into things that are meant to be internal, you may hit problems.

There is also a library for parsing MySQL binary logs in Ruby at, that, among other things,
allows an external software to extract meaningful row data from binary


Envisaged Binary Log ChangesRuedi Steinmann14 Dec
  • Re: Envisaged Binary Log ChangesStewart Smith17 Dec
    • Re: Envisaged Binary Log ChangesDavi Arnaut17 Dec
    • Re: Envisaged Binary Log ChangesMats Kindahl19 Dec