- 🇳🇿New Zealand quietone
@kingandy, Thank you for the idea!
The proposal doesn't met the Criteria for evaluating proposed changes → . In this case, there is not demonstrated demand and support for the change.
Most of the database API functions (db_query, db_select, db_update, db_insert, db_delete, db_merge) are fairly simple wrapper functions that call Database::getConnection(). getConnection() takes two variables - $target and $key - and the API functions allow developers to include one of these ($target) in the $options array. This allows a developer to switch between the default and slave within a cluster, but not name a database to operate on.
Presently the only way to switch between databases is to either call db_set_active() before and after our queries, or perform the getConnection() calls directly. It would be useful to be able to include a $key in the $options array as well, which would be passed directly through to the getConnection() call.
Apologies if this has been raised and discarded before, I had a look through the queue and there didn't seem to be anything immediately obviously connected.
Closed: works as designed
11.0 🔥
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
@kingandy, Thank you for the idea!
The proposal doesn't met the Criteria for evaluating proposed changes → . In this case, there is not demonstrated demand and support for the change.