I haven't really studied database design past the basics, but I'm currently designing an application that what looks like I'll need a lookup table between two tables, one being a regular table and one already being a lookup table. I'm wondering, is this alright or is something wrong with my design if I suddenly need to do a many to many relationship with a lookup table?
Here is an illustration if the above paragraph is confusing:
Table1 -----< Lookup Table1 (Table1 + Table2) >----- Table2
Table3 -----< Lookup Table2 (Table3 + Lookup Table1)
Is this a normal thing or is there a flaw in my design if this is occurring?
pretty hard to diagnose logical issues in a design littered with secret tables called "table this" and "table that"
with no regard to what they might contain, then yes, your design is perfectly fine
Thanks, I was just wondering if that type of relationship can exist. I don't believe my design is flawed which is why it went this way and no other way. I thought I would save you guys from posting the design of the actual database because I would have to post like 10 different tables for it to make sense.
This topic is now archived. It is frozen and cannot be changed in any way.