Sorry if my question is no appropriate for DA.
I have a State-city
table with unique id for every town/city name. (id: town --> city --> State)
I also have a list of Store names associated to each town. (less than 20 Stores for each town). Call this table Stores
In my app, I want users to register. I will store them in another table call Users
.
In my app I have a button allow users to take queue number for their selected town.
Now I don't know how to put these tables together for queue such that:
- One can save (for 1 month) each day's queue table of each towns with all details.
- One can add or remove a customer to each queue when Store is online,
- The size of the database is important for me.
Do you recommend to take town of users when they register? I have no idea whether this is a useful information or not.
My idea is that for each day and each town I should create a table (probably using join
but how to save this table?) with unique name e.g. id-of-town + date
(so how can one add date to table name?) then add customers id, town id and store id to this table. What is your solution?
Edit: I expect the final database size to be less or around 1 GB. Also, my estimate of the number of stores is 1000 (within 1 year from launch) and ideally it would be up to 1.5 million stores. (after years). From the comments it looks like I need to create a table for each store.
2022-12-18
. Is that Ok?