I am trying to create a database for an internal store that we are developing to manage our internal items (like phones, computers, office equipment, etc). The issue Ive run into is that they want each item to be able to support add-ons. The only issue I have with this is they also want the prices to be dynamic based on your region for both items and addons. So a different region may have a different price than some other region. The Items table right now supports this through a foreign key to the Availabilities table. What is the best practice to get the Addon's table to be a foreign key on the Availabilities table so that it to can have multiple prices per region? Is my design totally messed up here?
- Sql-server – Design concerns for using 3x bit or one char(1) or one integer in table for holding status of item
- Inventory Management DB Design
- Postgresql – Help with design of sales database
- Fact to Fact relationship in DW Design
- Designing a table with multiple column types and different foreign keys
- Mysql – Warehouse storage system (FIFO by BBD and date)
- Database design for product purchase history