On Apr 27, 2012, at 13:06 34, Wayne Merricks wrote:
Just wondering if this is something anyone has seriously thought about?
Very much so. In fact, implementing precisely these features (fully automatic
and seamless failover and recovery) for both the DB and audio store are
top-of-the-list
SELECTs can cause writes - if they require temporary tables to resolve.
This is quite often the case in MySQL, it being none too bright about
how it resolves complex queries (particularly ORDER BY queries where no
index exists). This is why master-master can be very tricky.
The only good
Hi.
I saw in another thread, that failover for DB was one of the
top-of-the-list goals for RD 3.x.
Maybe you'll share with us, what the other goals for RD 3.X is. It
would be very interesting to read.
Thank you!
Kind regards,
Morten
___
