On Jan 9, 2008 6:16 AM, Aaron Trevena <[EMAIL PROTECTED]> wrote:

> Hi All,
>
> Back in october there was some discussion of handling replication -
> and as with Bert and other's situations, I need to be able to specify
> when to user master/slave per query (or per method/function) due to
> replication lag.
>
> I didn't spot any mention of this in the Changelog - and Bert
> mentioned he needed it, so has any progress been made, or is there a
> workaround/manual way of doing it?
>
> Cheers,
>
> A.
>

Hey Aaron,

My thoughts on this, which were never implemented but it's a pretty trivial
thing to do, is that if you are inside of a transaction (look at transaction
depth) then to use the write source.  Other options that were proposed where
to have a "timeout" period where the read source is mapped to the write
source.

I tend to just think that transactions are the way to go, and to keep things
sane that way but I do understand that you can't always code that way in
existing systems.

I'm happy to act as a sounding board, but no longer at the job that I was at
when I was trying to solve this issue and have since picked up other higher
priority tasks.

-J

-- 
J. Shirley :: [EMAIL PROTECTED] :: Killing two stones with one bird...
http://www.toeat.com
_______________________________________________
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