# Beste conventie voor aangepaste plugin DB-gegevens voor 2021?

**URL:** <https://meta.discourse.org/t/best-convention-for-custom-plugin-db-data-for-2021/183521>\
**Category:** Development\
**Created:** [17 maart 2021 om 12:20 UTC](https://meta.discourse.org/t/best-convention-for-custom-plugin-db-data-for-2021/183521 "2021-03-17T12:20:46Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [17 maart 2021 om 12:37 UTC](https://meta.discourse.org/t/best-convention-for-custom-plugin-db-data-for-2021/183521/2 "2021-03-17T12:37:15Z")

</div>

> [@Zach\_Swinehart](#):
>
> It seems that custom migrations and tables are discouraged and that it’s generally better to either use custom fields or PluginStore

That may have been the case in early days, but nowadays it’s quite the opposite. We even migrated our own plugins from custom fields to their own tables were it made sense, like the poll plugin and the voting plugin.

Plugins with rich data models should create their own models, tables, relationships and migrations. It’s much maintainable and will provide great performance. Just watch for those N+1 😉

---

_[View the full topic](https://meta.discourse.org/t/best-convention-for-custom-plugin-db-data-for-2021/183521)._
