Deprecated notify change tracking policy #6586

Closed
opened 2026-01-22 15:35:23 +01:00 by admin · 1 comment
Owner

Originally created by @beberlei on GitHub (Dec 8, 2020).

As apparent in #6380 and #6564 the notify change tracking policy has issues and no performance gains over deferred explicit. It should be deprecated during 2.* in some form and removed in 3.

Originally created by @beberlei on GitHub (Dec 8, 2020). As apparent in #6380 and #6564 the notify change tracking policy has issues and no performance gains over deferred explicit. It should be deprecated during 2.* in some form and removed in 3.
admin added the Deprecation label 2026-01-22 15:35:23 +01:00
admin closed this issue 2026-01-22 15:35:23 +01:00
Author
Owner

@Arkemlar commented on GitHub (Aug 22, 2024):

Then, how do we force doctrine to update fields like json that holding nested objects? Specifically I'm talking about this case, which is suggesting to use clone, but that's kind of ugly.
Would be nice to be able to stay in deferred policy but explicitly set property as updated when needed. At the moment this would require dirty UOW hacks from the client-side code :(

@Arkemlar commented on GitHub (Aug 22, 2024): Then, how do we force doctrine to update fields like json that holding nested objects? Specifically I'm talking about [this case](https://github.com/dunglas/doctrine-json-odm?tab=readme-ov-file#limitations-when-updating-nested-properties), which is suggesting to use clone, but that's kind of ugly. Would be nice to be able to stay in deferred policy but explicitly set property as updated when needed. At the moment this would require dirty UOW hacks from the client-side code :(
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#6586