22848 Posts in 9643 Topics by 2803 members
|Go to End|
31 October 2010 at 7:08am
Not sure where else I would post this question, so posting it to general.
Have a client who is using a heavily customized SS 2.3.2. They are running into DB performance issues and would like the ability to make all of the DB writes use one DB connection (a master db), and most/some reads use a different DB connection (a slave db).
Basically, they would want the ability to include which db connection to use at the method call level. So for instance, DataObject::get() would become DataObject::get_using_dbconn() with an additional argument specifying the database connection to use.
Has anyone ever had the need to do something like this with SilverStripe before? Is there support in the code base to handle this?
If not, can anyone point me in the right direction to try and satisfy this request?
Thanks in advance.
1 November 2010 at 11:16pm
This thread might help...
|Go to Top|