[PR #10097] fix: readonly property's Entity deletion #12088

New Issue

admin · 2026-01-22T16:12:53+01:00

admin commented

2026-01-22 16:12:53 +01:00

Original Pull Request: https://github.com/doctrine/orm/pull/10097

State: closed
Merged: No

fixes #10032

What ultimately happens if an entity has its identifier not nulled? What happens in a world where every Entities in a project have readonly identifiers and therefore aren't nulled? What about non nullable but writable identifiers?
On a more general design, should we treat an Entity with a readonly identifier as we do for a readonly Entity?
What is the minimal PHP version for orm? 7.4? How will behave the isReadOnly() method on PHP < 8.1?

**Original Pull Request:** https://github.com/doctrine/orm/pull/10097 **State:** closed **Merged:** No --- fixes #10032 - What ultimately happens if an entity has its identifier [not nulled](https://github.com/doctrine/orm/blob/2.13.x/lib/Doctrine/ORM/UnitOfWork.php#L1252)? What happens in a world where every Entities in a project have readonly identifiers and therefore aren't nulled? What about non nullable but writable identifiers? - On a more general design, should we treat an Entity with a readonly identifier [as we do for a readonly Entity](https://github.com/Nayte91/orm/blob/cc6c38b8b0f084a6fff49396ef96ec1c03b57c5e/lib/Doctrine/ORM/UnitOfWork.php#L853)? - What is the minimal PHP version for orm? 7.4? How will behave the [isReadOnly()](https://github.com/Nayte91/orm/blob/cc6c38b8b0f084a6fff49396ef96ec1c03b57c5e/lib/Doctrine/ORM/UnitOfWork.php#L3423) method on PHP < 8.1?

admin added the pull-request label 2026-01-22 16:12:53 +01:00

admin referenced this issue

2026-01-22 16:17:11 +01:00

[PR #12088] Quote parts of the table name #13466

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: doctrine/archived-orm#12088