# How to plan out your database

**URL:** <https://community.glideapps.com/t/how-to-plan-out-your-database/68740>\
**Category:** Ask for Help\
**Created:** [December 15, 2023, 4:08pm UTC](https://community.glideapps.com/t/how-to-plan-out-your-database/68740 "2023-12-15T16:08:00Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [December 15, 2023, 4:15pm UTC](https://community.glideapps.com/t/how-to-plan-out-your-database/68740/2 "2023-12-15T16:15:19Z")

</div>

> [@Best Option for User Selection Lists (Single-Select or Multi-Select)](https://community.glideapps.com/t/best-option-for-user-selection-lists-single-select-or-multi-select/67546):
>
> What is the most effective approach for managing lists used for user selection? Is it better to have a single table where the different option types are listed in separate fields or columns, or should multiple tables be used, one for each type? What are the advantages of each option? As I continue to develop the project, I find that I’m incorporating a combination of both options as I occasionally reconsider my initial decision.

---

_[View the full topic](https://community.glideapps.com/t/how-to-plan-out-your-database/68740)._