Home/ Questions/Q 3319732
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T22:51:34+00:00

Stores Table : a table to store information about different stores StoreId Name PlaceCode

  • 0

Stores Table : a table to store information about different stores

StoreId     Name       PlaceCode  
--------    --------   --------     
1           Addidas     AB1         
2           Nike        KS3         
3           Puma        LS6         
4           Nike        AS2         
5           Nike        WR4

Areas Table

AreaId   Area
------   -------
1        DownTown
2        UpTwon

StoresArea Table :
Edit

StoreId   AreaId
-------   -------
1         1
2         2
3         2
4         1
5         2

Nike for example has more than a branch for it’s store
so my idea was to have more than a record with name attribute “nike” but the other attributes will contain the information about the branch.

I used the StoresArea Table to create a many-to-many relationship but I think it can be achieved with a one-to-many relation…and it’s confusing, so I was hoping for a good advice so it could help me follow a good practice!

I created a class named store, to hold the information about each store..but i want to add an additional variable and I think it will be an array, this variable will hold information about all the branches of a given store.

I think this information will be:
1 – the branch’s PlaceCode
2 – Id so I could provide a url using querystring to access all the other branches ?StoreId=Id
3 – the branch’s area
to go straight to the point, i want the detailed page of any given store to have a field called branches, which will display the Branch’s Area + the PlaceCode of all the other available branches. E.g “Branches : Downtown: AS2” and the Downtown word will be clickable to link to the branch!

I know It’s not clear enough! but I hope you’ll get it
sure, you can ask about any further details or questions make the picture more clear!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Kashef,

    Every store is only in a single region, correct? If so, create a store table with a foreign key relationship to the region table (i.e., RegionID in the store table).

    If different stores are part of the same brand/company, create a company table and set up a foriegn key to the store table.

    The setup would look like

    Region Table —> Stores <—- Company

    Is that the situation you have? If so, let me know and I’ll talk about the classes.

    Erick

    Edited based on comments

    In that case, what you really need a many-to-many relationship between Regions and Stores, with a distinct primary key (i.e., not RegionID + StoreID).

    Region Table —> RegionTable <— Stores <—- Company

    This will allow you to have multiple stores in a single region. However, it also allows multiple regions for a single store! You might be able to work around this with a constraint that ensures that each store only has a single region.

    Does this make sense?

    Erick

    • 0