Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
yosiasz
Master Smack Fu Yak Hacker
1635 Posts |
 Posted - 2010-04-12 : 14:38:10
|
| Hi thereJust reading that subject you probably are thinking "this guy is crazy". Assuming I am :) the user requires the following.For a specific business entity the user needs to put one or many restrictions on that entity. That entity could be how much money, how many hours they can spend on that entity. But now the user wants to add a non numeric restriction with a free text entry. The user has decided the restrictions should not be restricted but make them dynamic. So the design plan I have is as follows. Create a restrictions table Create a datatypes table Create a restrictions_datatypes table which join the above two tables which will have a unique row for restrictionID+datatypeIDCreate an entity_restrictions_datatypes which joins entity table and restrictions_datatypes. On front end user selects and entity, then a restriction and then a value for it.Have you ever encountered such a user requirement and do you think this appraoch is overkill or good?Thanks !!!<><><><><><><><><><><><><><><><><><><><><><><><><>If you don't have the passion to help people, you have no passion |
|
|
rebooot
Starting Member
9 Posts |
Posted - 2010-04-12 : 16:37:50
|
| This seems incredibly complicated to solve the problem you describe. Why not have two tables, one for the entity and another for the restrictions. The retrictions can have and ID and a Description and many other fields that you may choose to add to address any type of actions/reports you user may require. If I understand the problem you describe then a simple join would do. If not, you are going to have to eleborate on this a little more. |
 |
|
|
|
|
|
different data types for one field