You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My Versions table is fairly big and contains over 8-10M versions for this content_type. This query is very slow, unless an database index for (content_type, object_id) is added.
Do you think adding such an index might be considered as a feature?
Actually, my exact use case is a level more complicated. I need to produce an audit report, where I list all objects that have been changed. Then go through all the changes and filter out only the relevant ones.
Hello,
I have encountered a use case, where I need to query for all changes in some subset of tracked objects. Consider this example:
My Versions table is fairly big and contains over 8-10M versions for this
content_type
. This query is very slow, unless an database index for(content_type, object_id)
is added.Do you think adding such an index might be considered as a feature?
Actually, my exact use case is a level more complicated. I need to produce an audit report, where I list all objects that have been changed. Then go through all the changes and filter out only the relevant ones.
My approximate real code looks like this:
I wonder if there is a better approach to this.
The text was updated successfully, but these errors were encountered: