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

CY-3420 Passive_deletes for executions #2331

Merged
merged 2 commits into from Sep 4, 2020
Merged

CY-3420 Passive_deletes for executions #2331

merged 2 commits into from Sep 4, 2020

Conversation

tehasdf
Copy link
Contributor

@tehasdf tehasdf commented Sep 4, 2020

When deleting a deployment, the DB itself must do the cascade to executions,
because doing it on the python side takes too long, and that times out the request.
(with enough executions, of course)

Also, refactor passing in the backref into relationships a bit, so that this level
of configurability is actually possible

Instead of passing just the name, allow passing the whole object.
This will allow greater configurability, because now I can actually
configure the backref when creating a one_to_many_relationship
When a deployment is deleted, the db cascades the execution
by itself. No need to do it on the ORM side.
@tehasdf tehasdf merged commit e1589e7 into master Sep 4, 2020
@tehasdf tehasdf deleted the db-delete-cascade-1 branch September 4, 2020 11:13
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