On Sun, Apr 6, 2008 at 1:03 PM, Platonides <Platonides(a)gmail.com> wrote:
I was merely assuming a toolserver scenario.
Wrong list? :) A toolserver tool isn't an useful solution if we're
talking about software development, and isn't great even if we're only
talking about Wikimedia use (which there's no reason we should be).
So mysql is used, having
read access isn't a big deal and sensitive data isn't replicated (i think).
The sensitive data on the toolserver is cordoned off by views for
ordinary users. Roots can access all sensitive info, AFAIK. In fact,
if my understanding is correct, the toolserver uses the exact same
binlogs as the main cluster's slaves. At any rate, the binlogs are
going to be on the database servers, not the normal toolserver people
have access to.
Is it even possible to configure MySQL to only log certain statements,
within a given database or table? It seems like it would be
impractical. You would have to rewrite the UPDATE statements. If it
used row-based replication, that might be different, but that doesn't
work well with MySQL 4.0. :)
Plus, why keeping them forever? You probably only
want a small time
fraction, for tracking changes. Thus the new field would be useless for
many entries.
I guess you're not aiming very high with this. Undoubtedly someone
could hack up some toolserver thing, yeah. I'd be more interested in
talking about long-term, scalable solutions, properly integrated into
the software.