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.

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

enforce unique apps #205

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

enforce unique apps #205

wants to merge 1 commit into from

Conversation

calellowitz
Copy link
Collaborator

Since this can cause all sorts of issues, I think we want to enforce unique app ids for now. We will have to do some prep work to delete duplicates in the current db, but since those are broken anyway, that should be fine. When we implement r reusable apps, we can remove this constraint, but for now its a giant trap that can accidentally ruin someone else's opportunity.

@pxwxnvermx
Copy link
Contributor

We can also add the unique constraint to the learn_app and deliver_app columns on the Opportunity Model. That will ensure that no opportunties can reuse the apps from older opportunties.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants