Defining the data model
Our app has two clearly distinct entities:
- Stores
- Items to buy
Therefore, we will need two separate tables for them. The items to buy will need to be mapped to the stores as well as the status – Bought or To buy. Since we do not expect to have too many items in our list, we can maintain the status as simple text or even a Boolean field as there are only two values. However, in general, the recommended approach for fields that repeat is to set them using a picklist and, hence, define them in a separate table.
Will we need something else? No, that is all we need for now to enable the cases listed above.
