Issue Epic In Progress Quiet

#110794Align Extbase persistence with the core

Alexander Schnitzler 09/25/26, 16:38 updated 10/23/26, 05:44

Description

Problem

Extbase reads and writes records differently from the core in many places, and most of these differences are known only from single bug reports:

  • Deleting: removing an object loaded as its translation deletes the default record; deleting the default record leaves its translations; inline children without cascade remove stay.
  • Translations: the relations of a translation are written to the rows of the default record (MM reorder/remove); a new child of a translation gets language 0; synchronised fields and hideAtCopy are ignored.
  • Workspaces: an update inside a workspace writes the live row; count and LIMIT work on live rows before the overlay.
  • Reading: records per overlay mode, uids with overlays off, sorting, fallback chains and floating records differ from CONTENT and the Record API.
  • Field values: TCA eval, defaults, slug, uuid and native date columns are not applied the way DataHandler applies them.

The code that makes these decisions sits in three large classes (Typo3DbQueryParser, Typo3DbBackend, Backend), and the existing tests check SQL strings, not outcomes. A first approach pinned today’s Extbase behaviour in an outcome-based conformance suite (#110797, #110798). It turned out that pinning today’s behaviour also pins where Extbase is wrong, and a refactoring or a later persistence on doctrine/orm built on it would carry those errors along.

Goal

The core is the yardstick. For every topic there are pairs of functional tests on blog_example: a ByCore test does the action the way the backend or the frontend does it (DataHandler as admin, CONTENT, Record API), a ByExtbase test does the same through Extbase and expects the same result. While Extbase differs, the ByExtbase test is skipped with “Extbase differs from core: …”. The skipped tests are the work list: fixes make them pass, in a way that also works for a later persistence on doctrine/orm.

Sub-tasks

Step 1: pairs per topic (tests only)

One ticket and one patch per topic, below this epic:

  1. Removing records (translations, inline children with and without cascade remove, records without delete column, MM rows)
  2. Written field values (TCA eval, tstamp/crdate, defaults, uuid, slug, nullable and native date columns)
  3. Creating and changing translations
  4. MM relations of translations
  5. Inline, group and category relations
  6. To-one relations
  7. Reading relations (Record API)
  8. Reading translated records (CONTENT: overlay modes, uids, ordering, count, limit)
  9. Reading relations of translated records
  10. Reading and writing in workspaces
  11. Enable fields and visibility
  12. Constraints and operators
  13. Record types
  14. History, log and reference index
  15. Extbase-only behaviour without a core counterpart (fetch events, raw SQL statements, unsupported operators)

The tests of BehaviourConformanceTest (#110797, #110798) are replaced topic by topic by these pairs; tests that pin Extbase-only behaviour stay as plain Extbase tests.

Step 2: fixes

Each fix makes one or more skipped ByExtbase tests pass and removes their skip. Where a fix needs structure (one place for the language, workspace and visibility conditions, for the row overlay, for the write target), that structure is extracted as part of the fix.

Reference

Reviews 18

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". The changes above were merged or abandoned: read them before you start. How to create a patch

Commit message
[TASK] Align Extbase persistence with the core Resolves: #110794 Releases: main

Subtasks 17

History 26

Show 1 earlier messages
  1. Alexander Schnitzler changed tracker Story Epic TYPO3 Version 15 PHP Version 8.5 <span data-processor="relativetime" data-value="2026-09-25T16:43:03+00:00" > 09/25/26, 16:43 </span>

  2. Alexander Schnitzler changed subject Make Extbase persistence behaviour explicit and testable Align Extbase persistence with the core description <span data-processor="relativetime" data-value="2026-10-20T12:37:29+00:00" > 10/20/26, 12:37 </span>