DDC-343: Make it possible to force reloading of instanciated models #424

New Issue

admin · 2026-01-22T12:37:48+01:00

admin commented

2026-01-22 12:37:48 +01:00

Originally created by @doctrinebot on GitHub (Feb 16, 2010).

Originally assigned to: @beberlei on GitHub.

Jira issue originally created by user @lsmith77:

When doing bulk UPDATE/DELETE it might be useful to tell the EntityManager to either mark a model instance as "dirty" or even force immediate reload.
So for example:

i update all user models -> mark all user model instances as outdated or force reloading all of them at once
i update a list of user models and i have the list of ids -> mark a specific list of user model instances as outdated or force reloading of them at once
i do various updates, after i am done i want to force reloading of all model instances that are outdated or if a specific type or of a specific list of ids per type

In the same vain I might want to do similar things after bulk deleting.

Furthermore in some cases I might do inserts which could mean that a collection is no longer "valid". imagine for example i insert a new record and i have a hydrated collection over all of the models in the DB.

Originally created by @doctrinebot on GitHub (Feb 16, 2010). Originally assigned to: @beberlei on GitHub. Jira issue originally created by user @lsmith77: When doing bulk UPDATE/DELETE it might be useful to tell the EntityManager to either mark a model instance as "dirty" or even force immediate reload. So for example: 1) i update all user models -> mark all user model instances as outdated or force reloading all of them at once 2) i update a list of user models and i have the list of ids -> mark a specific list of user model instances as outdated or force reloading of them at once 3) i do various updates, after i am done i want to force reloading of all model instances that are outdated or if a specific type or of a specific list of ids per type In the same vain I might want to do similar things after bulk deleting. Furthermore in some cases I might do inserts which could mean that a collection is no longer "valid". imagine for example i insert a new record and i have a hydrated collection over all of the models in the DB.

admin added the New Feature label 2026-01-22 12:37:48 +01:00

admin closed this issue

2026-01-22 12:37:49 +01:00

admin commented

2026-01-22 12:37:50 +01:00

@doctrinebot commented on GitHub (Feb 16, 2010):

Comment created by @beberlei:

Since UPDATE and DELETE only allow WHERE clauses i guess it could be possible to pass a query hint that additionally generates a SELECT query and executes it right after the update/delete statement, in combination with HINT_REFRESH.

@doctrinebot commented on GitHub (Feb 16, 2010): Comment created by @beberlei: Since UPDATE and DELETE only allow WHERE clauses i guess it could be possible to pass a query hint that additionally generates a SELECT query and executes it right after the update/delete statement, in combination with HINT_REFRESH.

admin commented

2026-01-22 12:37:50 +01:00

@doctrinebot commented on GitHub (Feb 16, 2010):

Comment created by @beberlei:

@Lukas:

You can do it already, say you have:

UDPATE User u SET ... WHERE u.name = 'foo'

Just execute afterwards with $query->setHint(Query::HINT_REFRESH, true);

SELECT u FROM User u WHERE u.name = 'foo'

@doctrinebot commented on GitHub (Feb 16, 2010): Comment created by @beberlei: @Lukas: You can do it already, say you have: ``` UDPATE User u SET ... WHERE u.name = 'foo' ``` Just execute afterwards with $query->setHint(Query::HINT_REFRESH, true); ``` SELECT u FROM User u WHERE u.name = 'foo' ```

admin commented

2026-01-22 12:37:50 +01:00

@doctrinebot commented on GitHub (Feb 16, 2010):

Comment created by @lsmith77:

awesome! but it would also be nice to just mark as dirty. after all you may not be sure that you will actually need the updated versions in the current request or not.

@doctrinebot commented on GitHub (Feb 16, 2010): Comment created by @lsmith77: awesome! but it would also be nice to just mark as dirty. after all you may not be sure that you will actually need the updated versions in the current request or not.

admin commented

2026-01-22 12:37:52 +01:00

@doctrinebot commented on GitHub (Feb 16, 2010):

Comment created by @beberlei:

The problem is, UPDATE an dDELETE are directly translated into SQL. How do you know from there which objects to mark as dirty?

@doctrinebot commented on GitHub (Feb 16, 2010): Comment created by @beberlei: The problem is, UPDATE an dDELETE are directly translated into SQL. How do you know from there which objects to mark as dirty?

admin commented

2026-01-22 12:37:52 +01:00

@doctrinebot commented on GitHub (Feb 16, 2010):

Comment created by @lsmith77:

that would need to be custom user logic. i would tell the entitymanager to either mark all instances of a model type or only those with a specific list of id's.

@doctrinebot commented on GitHub (Feb 16, 2010): Comment created by @lsmith77: that would need to be custom user logic. i would tell the entitymanager to either mark all instances of a model type or only those with a specific list of id's.

admin commented

2026-01-22 12:37:52 +01:00

@doctrinebot commented on GitHub (Feb 26, 2010):

Comment created by @beberlei:

Hm, rethinking is - there isnt really a marking "dirty" possibility for entities, since you would have them throw exceptions upon access or something like this.

The underlying issue of this ticket is "fixed" though. Marking closed.

@doctrinebot commented on GitHub (Feb 26, 2010): Comment created by @beberlei: Hm, rethinking is - there isnt really a marking "dirty" possibility for entities, since you would have them throw exceptions upon access or something like this. The underlying issue of this ticket is "fixed" though. Marking closed.

admin commented

2026-01-22 12:37:54 +01:00

@doctrinebot commented on GitHub (Feb 26, 2010):

Issue was closed with resolution "Fixed"

@doctrinebot commented on GitHub (Feb 26, 2010): Issue was closed with resolution "Fixed"

admin referenced this issue

2026-01-22 15:58:44 +01:00

[PR #424] [CLOSED] Create the setCustomHydrationMode function #8169

admin referenced this issue

2026-01-22 15:58:45 +01:00

[PR #424] Create the setCustomHydrationMode function #8175

Sign in to join this conversation.