After we enabled the change notifier we found at least one case where automation repeatedly makes the same change to the database many times. This is silly, and unnecessarily invalidates caches. We should try to make clients smarter about this where we can, but we can also do better on the backend and simply check if things will change prior to making a write. We should watch out for potential performance penalties when it comes to Releases. Single locale updates already need to retrieve the current version of the blob before changing it, but updates to Release blobs that intend to replace the full contents may not already retrieve the entire blob already.
Priority: -- → P3
Ashish, are you still planning to look at this?
Not at the moment. Still busy with the gsoc project. So, I'll unassign the bug for now.
Can I try taking this on ?
Yup, go right ahead.
Assignee: nobody → svezauzeto12
(In reply to Ben Hearsum (:bhearsum) from comment #4) > Yup, go right ahead. Any progress here Tomislav?
Unassigning due to inactivity.
Assignee: svezauzeto12 → nobody
Hey!! Can you assign this one to me?? I would like to work on it.
(In reply to Vikas Prasad Mahato from comment #7) > Hey!! Can you assign this one to me?? I would like to work on it. Hi! Make a pull request and then we can change the assignment.
Sorry I was busy due to college. I would like to continue working on this bug. Can you give some hints on how should I proceed?
Hey! I am still interested in working on this bug. However I need some pointers on reproducing the bug.
You need to log in before you can comment on or make changes to this bug.