Master/Slave management

[Nobody/Anonymous]

How about some intelligence to issue SELECT statements to one set of servers (masters), but UPDATE/INSERT/etc statements to another set of servers (slaves)?

This would make it easy to manage MySQL style master/slave setups.

Many thanks for a great project!
-spod

[Frédéric RUAUDEL]

First, I'm happy that SQLB satisfy your needs. Thanks for using it.

I don't know this mysql features, but if you means something about database replication managed by Mysql, you can configure SQLB to use it but it will be a manual (not __intelligent__) procedure.

What you can do is to configure two connection in the config one to the __SELECT server__ and one to the __UPDATE/INSERT server__. Then in your program/script you make a wrapper function for select queries that send request to the __SELECT connection__ and another for insert/update queries that send their requests to the __INSERT/UPDATE connection__ (see some wrapper function for php in the documention section)

Despite this, I can't really do this kind of feature without breaking the goal of SQLB that is to make easier the switch between the different database without a big refactoring of the scripts that use it. But, if you can suggest me a way to do it and keep taking care of this, I'm listening ;)

If you have other question/suggestion, you are welcome !

GrumZ