I am building a database with primarily these two kind of stores:
a) Simple small family stores
b) Big and many branches stores
Those two kinds of stores are represented in a
Stores table; with the b) case I'm grouping them by same store with the
Branches table, something like this:
Stores table -> 'The Apparel Store'; IDStore 1 Branches table -> 'California Branch'; IDBranch 1; IDStore 1 Branches table -> 'Miami Branch'; IDBranch 2; IDStore 1 Branches table -> 'Texas Branch'; IDBranch 3; IDSTore 1
The problem for me is, is this a good approach for the single and small businesses? i.e. an Ice Cream family store in a neighborhood; I did think about just having these kind of stores in the
Stores table with just one record in
Branches table, but I'm worried about the simplicity of the design.
Simplicity in the sense that, I will have thousands of single little stores, they are just perfectly representated with only the Stores table. With that being said, also there is a small possibility the little ice cream store have another branch, you never know.
Is this the most simple yet flexible design?