0
In my ER model and diagram I created a specialization for an entity called clients, where it relates to the physical and legal entities derived from this specialization. I simply create the relationships between these tables as if it were a normal relationship or there’s something else I should do in the implementation?
1
It depends on the need, but that’s essentially it. You have the basic data in the person table and the specific data in the relationship type table (I imagine you will have other than customers, otherwise it doesn’t make much sense). The relationship takes place by a person ID on the client or with a client ID on the person (it would have to have a column for each type of relationship or some more elaborate trick). If you have something else to do I can not say, depends on the specific need not explicitly.
It is that I am creating a simple warehouse control software that will contain (as an extra), a sales routine where in turn could sell both to physical and legal customers, so I related so: seller<sales>customer; and customer, who findswhether as a specialised entity it relates to FISICO and JURIDICO. my need would be this. I say this because I just didn’t understand what I meant with other relationships besides clients.
Suppliers, sellers, employees, banks, government, carriers, etc. If all registered persons are customers there is no reason to specialize.
So just to end this debate, in what situation would you recommend the use of expertise? lack of experience in the software market makes me not see the need for certain functions, this is an academic project.
When you see no need, don’t use it. Specialization only makes sense with special cases, when some part of the data structure may vary depending on the situation.
Okay then, thanks for your help!
Browser other questions tagged sql database oop modeling
You are not signed in. Login or sign up in order to post.
Take a look at [tour], you can vote on everything on the site too.
– Maniero