I would never handle anything in code that could be done with the native
functionality of the DBMS.
Taco Fleur
Blog <http://www.tacofleur.com/index/blog/>
http://www.tacofleur.com/index/blog/
Methodology http://www.tacofleur.com/index/methodology/
0421 851 786
Tell me and I will forget
Show me and I will remember
Teach me and I will learn
I would argue that this problem falls outside the boundary of relational
database design for the most part, and instead falls within business logic.
To the best of my knowledge, there's no correct answer to this specific to
database design. In similar cases, I've simply added the Boolean field to
the primary table as you described, and relied on other logic within stored
procedures or application code to deal with keeping the intersection table
updated as appropriate.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
