[rel-DB] Sequential numbers cleanup#3174
[rel-DB] Sequential numbers cleanup#3174vkrasnovyd merged 20 commits intoOpenSlides:feature/relational-dbfrom
Conversation
b680a2e to
6c6ed51
Compare
676374c to
da1114e
Compare
|
|
hjanott
left a comment
There was a problem hiding this comment.
To make sure that in a meeting import with sequential number models old sequences are not applied. Just use some collection and assert that an unwanted value is overwritten with the next sequence number by the database anyway.
| self.assert_model_exists( | ||
| "assignment/1", | ||
| { | ||
| "title": "test_Xcdfgee", | ||
| "meeting_id": 110, | ||
| "open_posts": 0, | ||
| "phase": "search", | ||
| "sequential_number": 1, | ||
| }, | ||
| ) | ||
| self.assert_model_exists( | ||
| "agenda_item/1", {"meeting_id": 110, "content_object_id": "assignment/1"} | ||
| ) |
There was a problem hiding this comment.
Even though it's more lines, this way is so much easier to read. Love it.
Out of all the affected collections only |
|
Updated the meeting.import test to check the changes from OpenSlides/openslides-meta@a1d976c Added issue for the similar test in meta: OpenSlides/openslides-meta#336 |
|
Needs changes from OpenSlides/openslides-meta#343 |
ab93656
into
OpenSlides:feature/relational-db
Integrates changes from OpenSlides/openslides-meta#319
Current changes in the generation logic:
Other changes:
test_create_set_used_as_default_in_meeting_id. Reason - 1_1 trigger: now we can't have a meeting withoutused_as_default_projector_for_topic_in_meeting_id, so before the request we already have one.