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
{{ message }}
This repository has been archived by the owner on Feb 1, 2021. It is now read-only.
A shop that has been running for years might accumulate a huge quantity of outdated datas: logs in ps_log table, emails of users who have not shopped for a long time, abandoned carts, cart rules with single usage that have been used a long time ago ...
All of these SQL rows will stay there and make SQL queries being run against the database slower.
Describe the solution you'd like
Ideally ? PrestaShop would be able to identify "useless data" and suppress them. For example "logs that are X months old" (and merchant/webmaster can configure X).
Alternatives you've considered
a tutorial for merchants about how to identify and clean their old data
a tutorial for developers about how to identify and clean their old data
a warning system, able to monitor SQL tables size and properly warn developer/merchant about possible entanglement
Could be a pscleaner option. But i'm not sure about your last sentence, the size can depend on the server configuration, it's up to the user to settle it.
Is your feature request related to a problem?
A shop that has been running for years might accumulate a huge quantity of outdated datas: logs in
ps_log
table, emails of users who have not shopped for a long time, abandoned carts, cart rules with single usage that have been used a long time ago ...All of these SQL rows will stay there and make SQL queries being run against the database slower.
Describe the solution you'd like
Ideally ? PrestaShop would be able to identify "useless data" and suppress them. For example "logs that are X months old" (and merchant/webmaster can configure X).
Alternatives you've considered
Idea coming from @olecorre feedback
The text was updated successfully, but these errors were encountered: