A report after initial scanning through https://github.com/doctrine/dbal/releases/tag/4.0.0-beta1

• Table::changeColumn() renamed to Table::modifyColumn()
  

  pimcore/bundles/CoreBundle/src/Migrations/Version20211018104331.php

  Line 133 in c97929a

  $tableSchema->changeColumn($localForeignKeyColumn, [

• replace hasPrimaryKey with getPrimaryKey() in CMF migrations
  [Task]: Small change to make it compatible with DBAL v4 customer-data-framework#373

• replace getSchemaManager() with createSchemaManager()

• In bundle installers (eg.ecommerceframework, portal engine) replace createSchema with introspectSchema
  

  pimcore/bundles/EcommerceFrameworkBundle/src/Tools/Installer.php

  Line 412 in c7f023c

  return $this->schema ??= $this->db->getSchemaManager()->createSchema();

• replace $qb->execute with $qb->executeQuery
  

  pimcore/lib/Targeting/Storage/DbStorage.php

  Line 129 in c7f023c

  $stmt = $qb->execute();

  https://github.com/pimcore/pimcore/search?q=%24qb-%3Eexecute%28%29&type=code

Keeping this task on hold for the moment, as Symfony is not supporting yet for v4 (eg. Doctrine Messenger) making it difficult to test it

@kingjia90 But we could do already all the changes you listed above, right?

Blocker list:

• Can't use the query part getters anymore from the query builder , needs some refactor, especially for subqueries

  pimcore/lib/Model/Listing/Dao/QueryBuilderHelperTrait.php

  Line 160 in 9b560dc

  if ($query->getQueryPart($part)) {

  
  see also https://github.com/doctrine/dbal/blob/4.0.x/UPGRADE.md#deprecated-getting-query-parts-from-querybuilder
  https://github.com/doctrine/dbal/blob/4.0.x/UPGRADE.md#bc-break-changes-in-the-querybuilder-api
  • Custom views joins also relies on reading the FROM or table alias
  • Can't reset FROM part via resetQueryParts anymore, and only method is an array push, see [4.0] Query builder - how to reset From query part? doctrine/dbal#6371, trying with alternative https://github.com/pimcore/pimcore/pull/17003/files#diff-09de6410fb1e06d3d60e14877c348e74e247f47b13a4f4730bf76b9ff19bf744R216
• Waiting for ramsery uuid to support doctrine v4 in v2.1 or v3? feat: allow doctrine/dbal v4 ramsey/uuid-doctrine#247 for statistic explorer https://github.com/pimcore/statistics-explorer/blob/b59f20b19f4b4e24829ac8625c711151afc69211/composer.json#L25
• All $db->quote() where accepting mixed, but now are strictly string, also it's discouraged https://github.com/doctrine/dbal/blob/4.0.x/UPGRADE.md#bc-break-statementquote-only-accepts-strings
  • Probably can just add a deprecation, but to fully support it we need a major, see also 6b69787

Re-opening, needs a quick confirmation that would be fine to just getting closer to support v4 and if it would be possible to just support it in next major or must support both

We prepared for doctrine V4. The actual upgrade will happen in the next major release: #17096