You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Despite the fact that logic for splitting DB reads/writes is laid in settings.php and database.php (by $CONFIG->db->split = true; key in settings), core does not supports this feature correctly.
There is next logic in file "/engine/lib/database.php" at lines 30-52:
Despite that connection settings are prepared in variables $dbhost, $dbuser, etc. correctly, those variables are not used and connection established using direct values from $CONFIG.
Same situation can be seen in file "/simplecache/view.php" at line 25:
if ($mysql_dblink = mysql_connect($CONFIG->dbhost,$CONFIG->dbuser,$CONFIG->dbpass, true)) {
split logic isn`t used at all.
The text was updated successfully, but these errors were encountered:
This ticket is a duplicate of #1349 - split table support has not been added to Elgg - we should add some documentation so that people don't misinterpret what's there as full support.
Original ticket http://trac.elgg.org/ticket/1996 on 40214568-08-20 by trac user bios, assigned to unknown.
Elgg version: 1.7
Despite the fact that logic for splitting DB reads/writes is laid in settings.php and database.php (by $CONFIG->db->split = true; key in settings), core does not supports this feature correctly.
There is next logic in file "/engine/lib/database.php" at lines 30-52:
Despite that connection settings are prepared in variables $dbhost, $dbuser, etc. correctly, those variables are not used and connection established using direct values from $CONFIG.
Same situation can be seen in file "/simplecache/view.php" at line 25:
split logic isn`t used at all.
The text was updated successfully, but these errors were encountered: