There's a bit of discrepancy between what aspects of database API are key only and then inconsistent as to which order key and target are in the argument list. With 'default' being a common value for key and target this is going to get confused at some point.

from: grep key ./core/lib/Drupal/Core/Database/Database.php | grep function

Key only:

final public static function startLog($logging_key, $key = 'default') {
final public static function getLog($logging_key, $key = 'default') {

final public static function setActiveConnection($key = 'default') {
final public static function renameConnection($old_key, $new_key) {
final public static function removeConnection($key) {

Key followed by target.

public static function addConnectionInfo($key, $target, $info) {
final public static function getConnectionInfo($key = 'default') {
final protected static function openConnection($key, $target) {
public static function ignoreTarget($key, $target) {

Target followed by key.

final public static function getConnection($target = 'default', $key = NULL) {
public static function closeConnection($target = NULL, $key = NULL) {

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

danblack’s picture

Category: Feature request » Bug report
Status: Active » Needs review
FileSize
1.96 KB

$key, $target is the right way to do it as this is how its referenced in settings.php. Though its bad to switch the API a bit of consistency is called for.

Status: Needs review » Needs work

The last submitted patch, 1: issue-2225199.patch, failed testing.

marcingy’s picture

Priority: Major » Normal

This isn't major nothing is broken

danblack’s picture

Status: Needs work » Needs review
FileSize
15.62 KB

> This isn't major nothing is broken
quite right. Forgot to change this when I switch from Feature to Bug but even so major was excessive.

Status: Needs review » Needs work

The last submitted patch, 4: issue-2225199.patch, failed testing.

danblack’s picture

Status: Needs work » Needs review
FileSize
17.75 KB

Status: Needs review » Needs work

The last submitted patch, 6: issue-2225199.patch, failed testing.

danblack’s picture

Status: Needs work » Needs review
FileSize
18.47 KB
danblack’s picture

Issue tags: +API change
danblack’s picture

Do the core/includes/database.inc db_* functions need to have key and target?

jhedstrom’s picture

Version: 8.0.x-dev » 8.1.x-dev
Status: Needs review » Postponed

I think this would have to wait until 8.1, or perhaps even 9.0?

danblack’s picture

> I think this would have to wait until 8.1, or perhaps even 9.0?

Don't you think that will make things just much worse? If you fix it early before people start using it these inconsistent APIs would be my approach. By hey, given the slow attention to bugs I've given up.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

daffie’s picture

Version: 8.3.x-dev » 9.x-dev
Category: Bug report » Task
Status: Postponed » Needs review

A major +100 from me! It is very confusing. This is an API change and they are only allowed in a new major version.

catch’s picture

Version: 9.x-dev » 8.3.x-dev
Status: Needs review » Needs work

If 9.x only drops backwards compatibility with 8.x, then we need to consider how to do this in a bc-compatible way.

For example a new class with the new methods and deprecating the old one.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.