-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JTable->reorder is extremely slow #8189
Comments
Can you send your changes as pull request? So we can test, review and merge it easy? If you need help please see: https://docs.joomla.org/Using_the_Github_UI_to_Make_Pull_Requests This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8189. |
I can confirm, we are seeing same issue with 100,000 article DB, saving is extremely slow. Foreach doesn't cut it here. patch works for me. |
All credits for the patch should go to Michal Michaláč, who seems to be the author of the original patch.
Pull request created. |
It occurs to me that this has still not been fixed, after years in the wild, after submitting a patch, creating a pull request, and a long discussion about that very PR. We are still affected by this, and we're applying the very patch submitted here every single time we upgrade Joomla. This is becoming a huge problem and a strong argument for migrating off of to something else. Are there any plans to merge the PR or fix the bug in some other way? |
Every PR needs at least two testers before it can be merged. |
This is the PR: #8563 I thought it was linked here; there even was a discussion on the PR. |
This solution did NOT seem to make a difference in J v3.4.8 This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8189. |
@gitcubefree do test without seblod, because they use some additional call of "reorder" ... |
@gitcubefree can you test #8576 |
@Aleksandar-Todorovic Please mark your test result on https://issues.joomla.org/tracker/joomla-cms/8576 |
Closed as we have a PR #8576 This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/8189. |
This is an old issue that has never been properly solved. The original issue has been closed due to lack of testing.
Website I am running started having this issue, and we have verified that:
3.4.5
),We are using this patch in production on a high-traffic website. All credits for the patch should go to Michal Michaláč, who seems to be the author of the original patch.
GitHub does not allow me to attach a patch, so here it is, pasted:
The text was updated successfully, but these errors were encountered: