Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Does Target record need ManyToMany Project (Proposal) references? #1488

Open
alanbchristie opened this issue Aug 1, 2024 · 0 comments
Open

Does Target record need ManyToMany Project (Proposal) references? #1488

alanbchristie opened this issue Aug 1, 2024 · 0 comments
Assignees
@Waztom @mwinokan
Labels
backend stack

Comments

@alanbchristie
Copy link
Collaborator

alanbchristie commented Aug 1, 2024 •
edited
Loading

Work on #1485 exposed the fact that the current Target table has a project_id column, a ManyToMany relationship. The question is ... Can a Target record legitimately refer to more than one Project (Proposal)? If not the project_id record can be replaced by a simpler relationship.

Interestingly...

The existing (legacy) Production stack does have 16 Targets that have two Project relationships: -

FIH 2
GLUK1 2
NS3HEL 2
PGN_RS02895PGA 2
EBNA_A2 2
ADARB1A 2
Nprot 2
CD73 2
SERC 2
TCRUFPPS 2
UP1 2
GLUA2 2
HPRP 2
OXA10 2
PBP5 2
TIF6 2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Waztom Waztom

@mwinokan mwinokan

Labels
backend stack
Projects
Fragalysis
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Waztom @alanbchristie @mwinokan