One DB or Multiple

Question

question

deadreply asked Oct 26, '19

One DB or Multiple

Hi, im a newbi in conception of DB

Question, is better to put all model cars ex: lexus,audi,bmw... with model in one table or a table for each vendor ? for the future its more easy to work with one table or multiple.

Thanks

database model

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 1 · 2019-10-28T21:40:44Z

tonylodge answered Oct 28, '19

I would recommend one table to store a list of vendors and one table to store the models, referencing the correct vendor via a foreign key.

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 2 · 2019-10-29T22:02:05Z

deadreply answered Oct 29, '19

@tonylodge Ok but can you explain why this method ? thanks

1

10 |1200

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

tonylodge commented · Oct 30, 2019 at 10:14 AM

Sorry I wasn't very explanatory was I ?

It's all about good database design, you want each table to be a grouping of specific types of "things" or entities - could be customers, orders, in your case, cars etc.

So a vendor is a an entity, so is a car - hence seperate tables.

You don't want a different table for each car vendor because it would greatly complicate your queries when you want cars from more than one vendor, and it would mean adding a new table every time you added a vendor. You don't want to include vendor information in the car models table, because you will be repeating information.

It strikes me you could use some reading on the basics of database design. There are some good books out there but for a free starter I found this site:

Database structure and design

Hope this helps a little.

Best wishes,

Tony

1 ·

question