**Reported by VDigital on 3 Aug 2008 11:50**
**Version:** 1.7.2
A site with search as the first objective would have a very heavy search table.
Why keeping those so long?
[Piwigo Bugtracker #840](http://piwigo.org/bugs/view.php?id=840)
<!-- github-sync-id:97225538 -->
I Adding the ability to serve in this table maintenance bug:986
It is not enough that you propose
VDigital : You start a discussion on the Forum
**Comment posted by ddtddt on 29 Jul 2009 05:32**
I Adding the ability to serve in this table maintenance bug:986
It is not enough that you propose
VDigital : You start a discussion on the Forum
<!-- github-comment-id:124890813 -->
Not a real problem in my opinion. The search table is nothing compared to history. I computed some statistics on piwigo.com. In the first 10 days of March 2024, the most "searched" account has added 652 searches. That's 65 per day. Really not an issue.
Not a real problem in my opinion. The search table is nothing compared to history. I computed some statistics on piwigo.com. In the first 10 days of March 2024, the most "searched" account has added 652 searches. That's 65 per day. Really not an issue.
<!-- github-comment-id:2002543439 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Reported by VDigital on 3 Aug 2008 11:50
Version: 1.7.2
A site with search as the first objective would have a very heavy search table.
Why keeping those so long?
Piwigo Bugtracker #840
Comment posted by ddtddt on 29 Jul 2009 05:32
I Adding the ability to serve in this table maintenance bug:986
It is not enough that you propose
VDigital : You start a discussion on the Forum
Not a real problem in my opinion. The search table is nothing compared to history. I computed some statistics on piwigo.com. In the first 10 days of March 2024, the most "searched" account has added 652 searches. That's 65 per day. Really not an issue.