Special attribute for disjoint table

Question

1.00/5 (3 votes)

See more:

I have create clothing store database and I have made a disjoint table for Employees the employee is divided into vendor, customer service, Inventory representative I am a little bit confused for their special attribute so any recommendation concerning that

What I have tried:

special attribute for vendor is ability to negotiate

Posted 6-Dec-22 7:43am

Noran Azab

Updated 28-Apr-23 0:58am

PIEBALDconsult

v2

Add a Solution

Comments

PIEBALDconsult 6-Dec-22 13:58pm

Sounds like a homework assignment.
Otherwise, you're putting the cart before the horse. If you already had the attributes, you would know what strategy makes sense. In this case you seem to have decided on a strategy before you know the attributes. And that will lead only to failure.

Member 15627495 7-Dec-22 1:51am

you can have 'boolean' fields in a table.


negotiate:true|false

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Bohdan Stupak · Answer 1 · 2023-04-28T00:58:00

I think the structure is pretty straightforward. I'd have Occupation table with such fields as Id, Name, etc. The contents are vendor, customer service etc. And Employeetable which holds a reference to OccupationId.
If I understood your question correctly for some reason this structure doesn't suit you since you want to place it into a single table with columns like IsVendor, IsCustomerService but I can't see any advantage in such a structure since you might expect fairly big number of occupations and thus fairly big number of columns