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
a lot of core/sql (Aimeos\MShop\Index\Manager\MySQL) error in log #358
Comments
These are slow queries (time: >1000ms) and are likely due to your join of the mshop_stock table. Try to add an appropriate index to speed them up. |
ok, but I make this change according to your guide in the https://github.com/aimeos/aimeos-laravel/issues/url, please say me how can I add an appropriate index? |
You are doing something that Aimeos isn't optimized for and that doesn't mean that everything works perfectly out of the box. You have to use "EXPLAIN" for the queries that take long to find out where the problem is why MySQL needs so long and add indexes if possible to speed up the MySQL query. |
please keep in mind i did not do this on my own, i just made the changes you said, please visit this link: and I made these changes to my code. |
We removed that code again because of multiple issues. Our current solution would be to add an "in-stock" attribute to the products and remove it again if the stock level reached 0. This is something that can be done in a decorator for the stock manager. |
thanks for letting me know, in this case, I have a request from you, would you please help me?
|
Maybe but this has no priority for us and will only be available in 2021+
Sorry, we are not here to do your job. If you can't do it yourself, ask the Aimeos company. |
Since 2022.10, there's an |
Environment
Describe the bug
I upgraded from 2020.07 to 2020.10 and after but now I see a lot of errors in logs which I attach an screenshot of those.
why this happen and how can fix it?
Screenshots
Additional context
Please keep in mind in your direction (https://aimeos.org/help/post13262.html#p13223) I made changes to my files for filter products by stock level that you announced that this feature will be added in the next version.
The text was updated successfully, but these errors were encountered: