| |
@@ -8,7 +8,7 @@
|
| |
|
| |
from module_build_service.common.config import conf
|
| |
from module_build_service.common.models import (
|
| |
- session_before_commit_handlers, send_message_after_module_build_state_change
|
| |
+ session_before_flush_handlers, send_message_after_module_build_state_change
|
| |
)
|
| |
|
| |
__all__ = ("db_session",)
|
| |
@@ -19,7 +19,7 @@
|
| |
Starts listening for events related to the database session.
|
| |
"""
|
| |
event_hooks = (
|
| |
- ("before_commit", session_before_commit_handlers),
|
| |
+ ("before_flush", session_before_flush_handlers),
|
| |
("after_commit", send_message_after_module_build_state_change),
|
| |
)
|
| |
|
| |
Since ComponentBuildTrace(s) get created with db_session.commit() call,
is is not possible to commit more items in bulk if they already have been flushed.
Current unit-tests' setup can be significantly sped up if items can be quickly
flushed on the fly and bulk-commited only once at the end. Moreover in general it
seems more appropriate/safer to handle this in before_flush as any implicit
or accidental flush could cause new build traces not to be created at all. As flush
is implicitly called before every commit anyway, this change shouldn't pose any harm.