Matt S Trout wrote:
On Tue, Jun 03, 2008 at 06:49:59AM -0700, John Napiorkowski wrote:

--- On Tue, 6/3/08, Ian Docherty <[EMAIL PROTECTED]> wrote:

From: Ian Docherty <[EMAIL PROTECTED]>
Subject: [Dbix-class] master slave databases.
To: "Class user and developer list" <[email protected]>
Date: Tuesday, June 3, 2008, 8:31 AM
Hi
How would one go about configuring DBIC to direct all
writes to a Master database and all reads from a Slave database?

I am aware of  DBIx::Class::Storage::DBI::Replication but
is it used by anyone in a production environment such that it would not warrant the 'experimental' status?

Regards
Ian
There's a branch called "replication_redux" which is following trunk very 
closely and is a rewrite of the replication implementation.  We are using this (as of 
last Friday) on our production website and everything appears to be working correctly 
using mysql native replication.  Our site gets a lot of daily hits, so we feel it's 
shaping up solidly.

I'm writing up a more detailed overview for the mailing list, but wanted to get 
a few days in prod.   But if you need something like this I would enjoy 
collaboration and review.  Let us know more about what you are planning/needing.

How long do you need before this is ready now?

The previous vcersion of the code was already in production so there
shouldn't need to be -that- much rewriting to make it work, and 08100
should have shipped already and is being delayed for you.
I thought that things were quiet on the list. I seem to have missed several emails from the list so if anyone has asked me a question that I have not answered then I apologise now.

What should I understand by this response by mst about the current version of DBIC since I think I am reading the reply out of context.

Regards
Ian
_______________________________________________
List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class
IRC: irc.perl.org#dbix-class
SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/
Searchable Archive: http://www.grokbase.com/group/[EMAIL PROTECTED]

Reply via email to