When association caches are updated in the commit, the base value may be determined in the wrong revision. This can cause the creation of the base value to access objects deleted in the current commit and fail.

The problem is the inverse of #25770 - here a too new revision is accessed.

Test

• Unclear how this could be tested. The problem only occurs when the cache is not initialized until the commit completes. Observed the misbehavior at system startup after performing a migration.