Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Data Modeling advice
Message
From
06/12/2006 13:41:41
Cetin Basoz
Engineerica Inc.
Izmir, Turkey
 
 
To
06/12/2006 13:14:40
Keith Payne
Technical Marketing Solutions
Florida, United States
General information
Forum:
Microsoft SQL Server
Category:
Database design
Environment versions
SQL Server:
SQL Server 2000
Miscellaneous
Thread ID:
01174708
Message ID:
01175335
Views:
4
>
>Cetin,
>
>You couldn't join them separately either. E.g.
>
select * from endPoint e inner join Gadgets g where g.GadgetID = e.endPointID and g.endPointType = 'Gadget'
>might fail if the domains of GidgetID, GizmoID, and GadgetID are not identical. New features might alleviate the technical problems, but it is still an incorrect design that is tied to implementation and not to set theory.
>
>You don't need BindingNo1ID...nID in the design. If you use xref tables the joins will take care of themselves.

I was thinking along the lines of:
with wireBindings (wireID,Direction, gadgetID)
 as
(
 select wireID,Direction,endPointID from wired where endPointType = 'Gadget'
)
select * from wireBindings w inner join gadgets g on w.gadgetID = g.gadgetID
If gadgetID,gidgetID,gizmoID domains are not of the same type than I'd question the design.
Cetin
Çetin Basöz

The way to Go
Flutter - For mobile, web and desktop.
World's most advanced open source relational database.
.Net for foxheads - Blog (main)
FoxSharp - Blog (mirror)
Welcome to FoxyClasses

LinqPad - C#,VB,F#,SQL,eSQL ... scratchpad
Previous
Reply
Map
View

Click here to load this message in the networking platform