Wow thanks for the quick reply guys, sorry for not checking earlier!

Yes I was referring to what Lukas said (sending reads to a slave and
writes to a master). I already have MySQL Master-Slave replication
working on the database side.

I looked at MySQL Proxy a while ago but didn't want to add another
possible point of failure (plus it was still experimental when I last
looked at it, as Lee stated).

Since Propel started supporting this at version 1.3 (which was
released quite a while ago), I was hoping its functionality would be
integrated into the sfPropelPlugin, but alas...

If I find a "good" way to do it, I'll post it up.


On Mar 16, 10:41 pm, Lee Bolding <[email protected]> wrote:
> Ah. My bad :)
>
> If you want to play about with some advanced MySQL stuff, you *CAN* do  
> this natively with MySQL though (but it's still Alpha apparently)
>
> http://dev.mysql.com/doc/refman/5.1/en/mysql-proxy-cmdline.html
>
> :)
>
> On 16 Mar 2009, at 11:22, Lukas Kahwe Smith wrote:
>
>
>
> > On 16.03.2009, at 12:19, Lee Bolding wrote:
>
> >> This can be done natively with MySQL - check the MySQL docs
>
> >> On 16 Mar 2009, at 11:12, Nickolas Daskalou wrote:
>
> >>> Using: Symfony 1.2, Propel 1.3
>
> >>> Hi guys,
>
> >>> Does anybody know what is the best way to handle MySQL master-slave
> >>> replication in Symfony 1.2 using Propel 1.3?
>
> >>> There are plugins and code snippets available for older versions of
> >>> Symfony but nothing for 1.3.
>
> > I assume he is asking about automatically selecting a slave for read
> > transactions and using the master for write transactions.
>
> > regards,
> > Lukas Kahwe Smith
> > [email protected]
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to