Problem/Motivation

Drupal core has still lots of database specific logic that has not been moved to DTBNG. There are many parts of core that take conditional actions depending on which database backend is being used:

$db_type = Database::getConnection()->databaseType();
    if (in_array($db_type, ['mysql', 'pgsql'])) {
      $offset = '+00:00';
      static $already_set = FALSE;
      if (!$already_set) {
        if ($db_type == 'pgsql') {
          Database::getConnection()->query("SET TIME ZONE INTERVAL '$offset' HOUR TO MINUTE");
        }
        elseif ($db_type == 'mysql') {
          Database::getConnection()->query("SET @@session.time_zone = '$offset'");
        }

        $already_set = TRUE;
      }
    }

This prevents contributed database drivers from being able to fully support Drupal, and completely defeats the purpose of having a Database Abstraction layer.

How much code is affected? Doing a quick find-in-files of "databaseType()":

...\lib\Drupal\Core\Command\DbDumpCommand.php(138): if ($connection->databaseType() !== 'mysql') {
...\modules\path\tests\src\Functional\PathAliasTest.php(103): if ($connection->databaseType() != 'sqlite') {
...\modules\path\tests\src\Functional\PathAliasTest.php(257): if ($connection->databaseType() != 'sqlite') {
...\modules\simpletest\src\Tests\KernelTestBaseTest.php(345): if ($connection->databaseType() != 'sqlite') {
...\modules\system\src\Tests\Entity\Update\LangcodeToAsciiUpdateTest.php(30): if (Database::getConnection()->databaseType() !== 'mysql') {
...\modules\system\tests\src\Kernel\Scripts\DbDumpCommandTest.php(29): if (Database::getConnection()->databaseType() !== 'mysql') {
...\modules\views\src\Plugin\views\argument\StringArgument.php(183): if (Database::getConnection()->databaseType() == 'sqlite') {
...\modules\views\src\Plugin\views\argument\StringArgument.php(189): if (Database::getConnection()->databaseType() == 'pgsql') {
...\modules\views\src\Plugin\views\argument\StringArgument.php(215): if ($this->options['case'] != 'none' && Database::getConnection()->databaseType() == 'pgsql') {
...\modules\views\src\Plugin\views\argument\StringArgument.php(284): if ($this->options['case'] != 'none' && Database::getConnection()->databaseType() == 'pgsql') {
...\modules\views\src\Plugin\views\query\Sql.php(1758): $db_type = Database::getConnection()->databaseType();
...\modules\views\src\Plugin\views\query\Sql.php(1796): $db_type = Database::getConnection()->databaseType();
...\modules\views\src\Plugin\views\query\Sql.php(1819): $db_type = Database::getConnection()->databaseType();
...\tests\Drupal\KernelTests\Core\Command\DbDumpTest.php(83): $this->skipTests = Database::getConnection()->databaseType() !== 'mysql';
...\tests\Drupal\KernelTests\Core\Database\ConnectionTest.php(125): if (Database::getConnection()->databaseType() !== 'mysql' || !defined('\PDO::MYSQL_ATTR_MULTI_STATEMENTS')) {
...\tests\Drupal\KernelTests\Core\Database\ConnectionTest.php(162): if (Database::getConnection()->databaseType() !== 'pgsql') {
...\tests\Drupal\KernelTests\Core\Database\SchemaTest.php(66): if (Database::getConnection()->databaseType() == 'mysql') {
...\tests\Drupal\KernelTests\Core\Database\SchemaTest.php(189): $db_type = Database::getConnection()->databaseType();
...\tests\Drupal\KernelTests\Core\Database\SchemaTest.php(266): if (Database::getConnection()->databaseType() != 'mysql') {
...\tests\Drupal\KernelTests\Core\Database\SchemaTest.php(430): if (Database::getConnection()->databaseType() == 'mysql') {
...\tests\Drupal\KernelTests\Core\Database\SchemaTest.php(838): $db_type = Database::getConnection()->databaseType();
...\tests\Drupal\KernelTests\Core\Database\SelectComplexTest.php(236): $db_type = Database::getConnection()->databaseType();
...\tests\Drupal\KernelTests\KernelTestBaseTest.php(226): if ($connection->databaseType() != 'sqlite') {
...\tests\Drupal\Tests\Core\Database\Stub\Connection.php(47): public function databaseType() {

Proposed resolution

Remove any code in core that is in the form of:

   $db_type = Database::getConnection()->databaseType();
    if ($db_type == 'whatever') {
      // I'm not portable.
   }

Remaining tasks

Do it.

Child issues:

User interface changes

API changes

Data model changes

Comments

david_garcia created an issue. See original summary.

david_garcia’s picture

Issue summary: View changes
cilefen’s picture

I think this may be a task.

mondrake’s picture

Adding a first child issue. Maybe #2879677: Decouple getting table vs column comments in Schema also should be listed here? Even if it's more driver related than database related, though.

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.

mondrake’s picture

Issue summary: View changes

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.

larowlan’s picture

Category: Bug report » Task
Issue tags: +Bug Smash Initiative

Agree with cilefen that this is a task

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.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.