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

N2n regulation groups #403

Merged
merged 4 commits into from
Nov 28, 2024
Merged

N2n regulation groups #403

merged 4 commits into from
Nov 28, 2024

Conversation

LKajan
Copy link
Contributor

@LKajan LKajan commented Nov 28, 2024

Implements n2n relations between plan objects and regulation groups.

  • Removes lifecycle status change propagation from plan objects to regulation groups
  • Plan lifecycle status changes are propagated to regulation groups

This PR is based on #385
Depends on:

All these three should be merged before this one

Copy link
Contributor

@Rikuoja Rikuoja left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks really good, just a typo.

@LKajan LKajan force-pushed the n2n-regulation-groups branch 2 times, most recently from af47709 to 85797c9 Compare November 28, 2024 13:31
SqlAlchemy is not so happy of our choise to use same association table
for multiple tables. Therefore we must tell that multiple relations
overlaps and use the same regulation_group_id field.
Don't try to find lifecycle status from plan objects. In a creation time
regulation group might not belong to any plan object or it might belong
to many plan objects. There is no simply rule how to define from which
plan object the lifecylcle status is read from.

There is still a BI trigger that sets the lifecycle status from the plan.
Plan regulation groups and therefore regulations can belong to multiple
plan objects. This means that the lifecycle status of a regulation can't
be updated automatically when a plan object is updated.

Lifecycle status of regulations are still updated when a lifecycle status
of a plan is updated.
@LKajan LKajan force-pushed the n2n-regulation-groups branch from 85797c9 to 41a1d70 Compare November 28, 2024 13:38
@LKajan LKajan merged commit 9f568ce into main Nov 28, 2024
2 checks passed
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.

2 participants