I'm looking for some advice on best practice for dealing with replicated
MySQL databases.
My current client has a large database which is split across a RW master
and several RO slaves (I believe that's how MySQL replication always
works). They're just toying with replacing a lot of their
On Tue, Mar 24, 2009 at 8:23 AM, Dave Cross d...@dave.org.uk wrote:
I'm looking for some advice on best practice for dealing with replicated
MySQL databases.
My current client has a large database which is split across a RW master and
several RO slaves (I believe that's how MySQL replication
On Tue, Mar 24, 2009 at 08:23, Dave Cross d...@dave.org.uk wrote:
I'm looking for some advice on best practice for dealing with replicated
MySQL databases.
My current client has a large database which is split across a RW master and
several RO slaves (I believe that's how MySQL replication
Hi all,
I wrote once somewhere that DBIC shall use Moose sometime.
Do I remember this right? What are the plans?
If yes, is Moose used to build up the classes of DBIC or also
using the reflection features of Moose to make Moose-compatible
objects persistent?
Best regards
Andreas
Just wanted to ask if I'm right that I heard that DBIC wants to use Moose
in the future. And if yes, what are the plans.
The plan is that 0.09 will both use Moose and be very Moose-friendly.
When that will happen is largely dependent on people helping out. Come
help?
Thanks,
Rob
