# PluginStore might not always be preferred

**URL:** <https://meta.discourse.org/t/pluginstore-might-not-always-be-preferred/39480>\
**Category:** Development\
**Created:** [12 Febbraio 2016, 3:07pm UTC](https://meta.discourse.org/t/pluginstore-might-not-always-be-preferred/39480 "2016-02-12T15:07:17Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague)\
**Post date:** [16 Marzo 2016, 6:22am UTC](https://meta.discourse.org/t/pluginstore-might-not-always-be-preferred/39480/3 "2016-03-16T06:22:02Z")

</div>

> [@sam](#):
>
> we persist forever.

There should be a way to remove tables / rows if an Admin want to no?

My concern is due to experience with WordPress plugins.

They can be

- installed
- activated
- deactivated
- uninstalled

The problem comes from the fact that it is up to the plugin author to use the “uninstall hook” to do clean-up and many don’t do that.

Some create tables that become unused, and perhaps worse, many add rows to the “options” table.

No problem in small doses, but over time the table can become so full of orphans that there is a noticeable slowdown. WordPress being a heavy database app such as it is.

I’m not saying that the database should be automatically pruned, but I think it would be good if plugins offered a “pre-uninstall cleanup” type of thing.

---

_[View the full topic](https://meta.discourse.org/t/pluginstore-might-not-always-be-preferred/39480)._