Modeling Database

Asked

Viewed 43 times

1

I am doing a modeling for company and I am an intern. I studied a lot on the site that is in English... When I finished modeling there I went to show my modeling and they say I’m doing something wrong and I got weird.

Modeling: We have 300 phones that are equal model and manufacturer (LG K4), 50 (SAMSUNG GALAXY J2) and records data (imei1, imei2, phone1, phone2, etc)

That’s what I did:

List of layout

And they changed mine, it was like this: List of layout2 Second will have very registered.

Att, Carlos Oliveira

  • I don’t understand the cardinality of your relationships. A manufacturer points to a single cell phone? That’s right?

  • In my opinion your modeling is right and theirs is wrong. A cell phone must belong to a model and this must belong to a manufacturer. The diagram does not show the cardinality and this can eventually be improved. Modeling is more accurate if you consider that phone numbers are linked to SIM cards and these to mobile phones, which suggests a separate table for SIM cards.

  • From what I understood of their representation of relationship cardinality (the black ball represents the side N and the blue diamond the side 1) then the second model is clearly wrong. For example, it is assumed that a manufacturer manufactures several cell phones, as this would be represented in the model? A manufacturer would have multiple ID_FK_CELULAR, one for each appliance?

  • @Piovezan: Exactly, this is the way I want economy and faster.

  • @anonimo Exactly. I don’t really like that it would have multiple for nothing, because the cloud server has only 40 GB of space.

No answers

Browser other questions tagged

You are not signed in. Login or sign up in order to post.