Sfrgttk

Ubuntu Server install with full GUI

Have you ever entered Singapore using a different passport or name?

Why did Acorn's A3000 have red function keys?

Why do we hear so much about the Trump administration deciding to impose and then remove tariffs?

Can a flute soloist sit?

Origin of "cooter" meaning "vagina"

If a Druid sees an animal’s corpse, can they Wild Shape into that animal?

Did Scotland spend $250,000 for the slogan "Welcome to Scotland"?

Is an up-to-date browser secure on an out-of-date OS?

Can you compress metal and what would be the consequences?

Looking for Correct Greek Translation for Heraclitus

Is there a symbol for a right arrow with a square in the middle?

Why hard-Brexiteers don't insist on a hard border to prevent illegal immigration after Brexit?

Which Sci-Fi work first showed weapon of galactic-scale mass destruction?

Button changing it's text & action. Good or terrible?

Did 3000BC Egyptians use meteoric iron weapons?

Why can Shazam fly?

What does ひと匙 mean in this manga and has it been used colloquially?

What is the most effective way of iterating a std::vector and why?

Multiply Two Integer Polynomials

What are the motivations for publishing new editions of an existing textbook, beyond new discoveries in a field?

Am I thawing this London Broil safely?

How to manage monthly salary

Should I use my personal e-mail address, or my workplace one, when registering to external websites for work purposes?

More than one path between M-M tables

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

0

I'm trying to figure out if it is bad practice to have more than one path between tables that are related via many-to-many relationships.

I have 3 user-facing tables: Dupe, Cue, and Take. There is a many-to-many relationship between Dupes and Cues, and there is a many-to-many relationship between Takes and the join table Dupe_Cues.

The user can add, delete, and modify Cues, Dupes and Takes, and she can make links between Cues/Dupes and Cues/Takes, but there are also certain situations when the user will want to directly add a Take to a Dupe, without creating a cue. So I figure the simplest thing to do is create a Dupe_Take table. The problem is, I'm worried it will cause referential issues and isn't good database design.

If I don't create a Dupe_Take table, I suppose I could add a field to the Cue table, like "b_CreatedByUser". Then, whenever the user does a query, I filter out Cues where b_CreatedByUser=FALSE so that Cues that are only used to link Takes to Dupes are never shown to the user, but that sounds sloppy and difficult to maintain.

What is the best practice? What factors should I be considering?

Thanks for any advice.

referential-integrity many-to-many

share

asked 3 mins ago

slondikeslondike

1

New contributor

slondike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

0

I'm trying to figure out if it is bad practice to have more than one path between tables that are related via many-to-many relationships.

I have 3 user-facing tables: Dupe, Cue, and Take. There is a many-to-many relationship between Dupes and Cues, and there is a many-to-many relationship between Takes and the join table Dupe_Cues.

The user can add, delete, and modify Cues, Dupes and Takes, and she can make links between Cues/Dupes and Cues/Takes, but there are also certain situations when the user will want to directly add a Take to a Dupe, without creating a cue. So I figure the simplest thing to do is create a Dupe_Take table. The problem is, I'm worried it will cause referential issues and isn't good database design.

If I don't create a Dupe_Take table, I suppose I could add a field to the Cue table, like "b_CreatedByUser". Then, whenever the user does a query, I filter out Cues where b_CreatedByUser=FALSE so that Cues that are only used to link Takes to Dupes are never shown to the user, but that sounds sloppy and difficult to maintain.

What is the best practice? What factors should I be considering?

Thanks for any advice.

referential-integrity many-to-many

share

asked 3 mins ago

slondikeslondike

1

New contributor

slondike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

add a comment | 

I'm trying to figure out if it is bad practice to have more than one path between tables that are related via many-to-many relationships.

I have 3 user-facing tables: Dupe, Cue, and Take. There is a many-to-many relationship between Dupes and Cues, and there is a many-to-many relationship between Takes and the join table Dupe_Cues.

The user can add, delete, and modify Cues, Dupes and Takes, and she can make links between Cues/Dupes and Cues/Takes, but there are also certain situations when the user will want to directly add a Take to a Dupe, without creating a cue. So I figure the simplest thing to do is create a Dupe_Take table. The problem is, I'm worried it will cause referential issues and isn't good database design.

If I don't create a Dupe_Take table, I suppose I could add a field to the Cue table, like "b_CreatedByUser". Then, whenever the user does a query, I filter out Cues where b_CreatedByUser=FALSE so that Cues that are only used to link Takes to Dupes are never shown to the user, but that sounds sloppy and difficult to maintain.

What is the best practice? What factors should I be considering?

Thanks for any advice.

referential-integrity many-to-many

share

asked 3 mins ago

slondikeslondike

1

New contributor

slondike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share

asked 3 mins ago

slondikeslondike

1

New contributor

slondike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share

asked 3 mins ago

slondikeslondike

1

New contributor

slondike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 3 mins ago

slondikeslondike

1

New contributor

slondike is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 3 mins ago

slondikeslondike

1