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 |
|
KnooKie
Aged Yak Warrior
623 Posts |
 Posted - 2002-01-10 : 05:56:58
|
| i have a table 'version' which has the following fields: fl_versionRO, fl_versionUpdate, fl_VBversionThis table only has one record in it which is the version of various front-ends which hang off the database.What is the best way to define the relationship to hang another table off this one on the many side but where it could hang off any one of the three fields mentioned above. i.e. it could be one-to-many: version.fl_versionRO to <othertable>.fl_versionROORone-to-many: version.fl_versionUpdate to <othertable>.fl_versionUpdateORone-to-many: version.fl_VBversion to <othertable>.fl_VBversionHope that's clear ? What is the correct way to do this if indeed there is one. Is leaving it as a stand-alone table specifying the relevant JOIN in queries ok for this scenario ? Data will never be deleted from this table.I am using SQL7.thankeePaulEdited by - knookie on 01/10/2002 06:03:09Edited by - knookie on 01/10/2002 06:09:27 |
|
|
Nazim
A custom title
1408 Posts |
Posted - 2002-01-10 : 10:10:32
|
quote:
leaving it as a stand-alone table specifying the relevant JOIN in queries ok for this scenario
IMHO ,That sounds ok to me. you can create relationships too.coz, otherwise if you dont keep this table seperate it will end up giving the pitfalls of a unnormalized database.----------------------------Anything that Doesn't Kills you Makes you Stronger |
 |
|
|
|
|
|
Table design