Problem/Motivation

Follow up of #3200743: Decouple identifier management from database Connection, introduce an IdentifierHandler class

Use Table identifier value objects instead of table name strings in database Schema classes

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Issue fork drupal-3514117

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

mondrake created an issue. See original summary.

mondrake opened merge request !11539

mondrake’s picture

mondrake
Location 🇮🇹
commented
Title: [PP-1] Use Table identifier value objects instead of table name strings in database Schema classes » [PP-2] Use Table identifier value objects instead of table name strings in database Schema classes
Related issues: +#3514261: [PP-1] Allow using Table identifier value objects in database Query classes

Better do this after #3514261: [PP-1] Allow using Table identifier value objects in database Query classes.

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.