Re: Envisaged Binary Log Changes

Ruedi Steinmann <[email protected]> writes:
> We are planning to build an asynchronous data-warehouse (we hope to 
> achieve 0.1-1s delay). We use a MySQL database for our production system 
> and would like to use the binary log of MySQL to keep the warehouse 
> up-to-date.
>
> Are there any substantial changes to the BinLog envisaged which could 
> render the binlog useless for our purpose?

While Oracle is unlikely to comment on future directions, I can provide
a pretty well educated guess.

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).

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.

My advice would be: you're safe if you don't upgrade, and it's a much
better plan to use binlog as a trigger to run normal SQL queries to
populate your data warehouse rather than using the binlog itself to
populate it.

-- 
Stewart Smith

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBAgAGBQJQzmHcAAoJEP08notdpDyvsa8P/Rtd5+OPlH82lc+ujjyGPcCg
3/kQWokuh37Q+wZYesjbMe9jn4jX8brSyODd9+F+v/wcJM5z1vdfpc6AHeB6peh3
/UBVS/4kfWbqX5qvrhmwOb7iYBtuFTg9VXyjTDy7BYXq9pd+lNhPoyy7H9dwN5uw
7LvTuT63gziTuyHMiW4+x2BX1RzwjasWZUnDMfRHYU+fIdqdHVGICWYc2ATj0mpw
/7CQqiMz1jFl2mPMxCQ9FBSuInNeIlAqZ4G5pAmcySCW6FDOEleV6vQ8ZpKL4YuK
H+v0ck3+Ifmf+wXL3Kw64QBbcPgI8UeXNhYn8KSivC9KEF6d0linzJsnaJ7VLW9g
AAR6GJp4AofOgidqAHHC3N/8P6+6jzqYiYMMROiPt5leYY0D6EQvYYYrSi2NBws+
RBKAnL9wezdMjTopJzer97GK6RWKGydVaDcqy3+Yjk9DHLhU+53om/3avD4OOB1i
Z3w4Dx3U3fn9sxBumu/HPPI+xj1Wke5yckAs9Rzc6iZoehGwBga93z0n6ZByu5sD
cYNqgseS/ctaE5WEWDNMxa/iZboHJoV5hB+304F47bPcMn3ratb6GdPv2Mc1ADj5
iqmclquvRNuDqHBJP2fZrLCGB0ZBrMuf82NQTtkcewZ/m1SothtW/LLicO0bc+85
2d0B2wxPbdh3qNqg42Lb
=DNxO
-----END PGP SIGNATURE-----