Pressflow has become very popular among midsize and large sites. It uses a dedicated variable, $db_slave_url, for collecting the database connection strings of slave dbs. Our reports should be able to run against these slaves. customreports already can use non default databases but not those specificied by pressflow.
i will soon be adding this feature. feedback welcome. see https://wiki.fourkitchens.com/display/PF/Using+database+replication+with... for more detail on pressflow's implementation.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | customreports-1067808.patch | 1.72 KB | Race.it |
| #6 | customreports-1067808.patch | 1.42 KB | Race.it |
| #4 | customreports-1067808.patch | 1.42 KB | Race.it |
| #1 | customreports-1067808.patch | 891 bytes | Race.it |
Comments
Comment #1
Race.it commentedI have created a patch for this, let me know if its sufficient?
Comment #2
moshe weitzman commentedAwesome. Thanks.
Do folks have a need to run some reports on the master and some on the slave? Seems like a pretty exotic need so this patch should suffice. We should add the URL I pasted to the code comment so folks learn about pressflow's slave support.
Comment #3
moshe weitzman commentedI think this patch is incompatible with the 'use foo' trick. See code just above this one. We should put this code in an else against that code or otherwise make them work together better.
Comment #4
Race.it commentedMy bad, I had used the head for the patch, I have now rerolled the patch against the 6.x-1.x-dev branch.
Comment #5
moshe weitzman commentedthx. just a typo now: instalation
Comment #6
Race.it commentedNew patch with installation spelt right :)
Comment #7
Race.it commentedChange the patch files comments around, so the comments are more structured.
Comment #8
moshe weitzman commentedCommitted to 6.x. Thanks.