I have a data collection script which rolls raw data into a formatted
table, based on year/month/day. I've been requested to roll up this raw
data based on a different timezone - 3 hours behind - to better coincide
with reports from a company in that timezone.
This is the rollup SQL query we
At 01:07 PM 11/13/01 -0600, Gerald Clark wrote:
Start the server with the desired TZ set.
That's all fine and good, but difficult switch back and forth every 10
minutes while that query runs for local data, then for the remote data.
I have a fairly complicated one-way replication set-up, whereby we have
multiple master servers and multiple slaves, all replicating unrelated
databases from one to another.
It's set up and works, but not reliably. Pretty much every day I come into
work to find one machine is no longer
I tested replication recently and found it extremely lacking. Even the
most minor of errors causes the daemon to stop replicating, effectively
rendering the ability useless to me, as I use mysql for authentication.
Is there some configuration command to make it *ignore* errors and continue
to
