Signals
Signals are a mechanism to fire your piece of code (function / method) whenever given type of event happens in ormar
.
To achieve this you need to register your receiver for a given type of signal for selected model(s).
Defining receivers
Given a sample model like following:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 |
|
You can for example define a trigger that will set album.is_best_seller
status if it will be played more than 50 times.
Import pre_update
decorator, for list of currently available decorators/ signals check below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 |
|
Define your function.
Note that each receiver function:
- has to be callable
- has to accept first
sender
argument that receives the class of sending object - has to accept
**kwargs
argument as the parameters send in eachormar.Signal
can change at any time so your function has to serve them. - has to be
async
cause callbacks are gathered and awaited.
pre_update
currently sends only one argument apart from sender
and it's instance
one.
Note how pre_update
decorator accepts a senders
argument that can be a single model or a list of models,
for which you want to run the signal receiver.
Currently there is no way to set signal for all models at once without explicitly passing them all into registration of receiver.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 |
|
Note
Note that receivers are defined on a class level -> so even if you connect/disconnect function through instance
it will run/ stop running for all operations on that ormar.Model
class.
Note that our newly created function has instance and class of the instance so you can easily run database queries inside your receivers if you want to.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 |
|
You can define same receiver for multiple models at once by passing a list of models to signal decorator.
1 2 3 4 |
|
Of course, you can also create multiple functions for the same signal and model. Each of them will run at each signal.
1 2 3 4 5 6 7 |
|
Note that ormar
decorators are the syntactic sugar, you can directly connect your function or method for given signal for
given model. Connect accept only one parameter - your receiver
function / method.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
|
Warning
Note that signals keep the reference to your receiver (not a weakref
) so keep that in mind to avoid circular references.
Disconnecting the receivers
To disconnect the receiver and stop it for running for given model you need to disconnect it.
1 2 3 4 5 6 7 8 9 10 |
|
Available signals
Warning
Note that signals are not send for:
-
bulk operations (
QuerySet.bulk_create
andQuerySet.bulk_update
) as they are designed for speed. -
queryset table level operations (
QuerySet.update
andQuerySet.delete
) as they run on the underlying tables (more like raw sql update/delete operations) and do not have specific instance.
pre_save
pre_save(sender: Type["Model"], instance: "Model")
Send for Model.save()
and Model.objects.create()
methods.
sender
is a ormar.Model
class and instance
is the model to be saved.
post_save
post_save(sender: Type["Model"], instance: "Model")
Send for Model.save()
and Model.objects.create()
methods.
sender
is a ormar.Model
class and instance
is the model that was saved.
pre_update
pre_update(sender: Type["Model"], instance: "Model")
Send for Model.update()
method.
sender
is a ormar.Model
class and instance
is the model to be updated.
post_update
post_update(sender: Type["Model"], instance: "Model")
Send for Model.update()
method.
sender
is a ormar.Model
class and instance
is the model that was updated.
pre_delete
pre_delete(sender: Type["Model"], instance: "Model")
Send for Model.save()
and Model.objects.create()
methods.
sender
is a ormar.Model
class and instance
is the model to be deleted.
post_delete
post_delete(sender: Type["Model"], instance: "Model")
Send for Model.update()
method.
sender
is a ormar.Model
class and instance
is the model that was deleted.
pre_relation_add
pre_relation_add(sender: Type["Model"], instance: "Model", child: "Model",
relation_name: str, passed_args: Dict)
Send for Model.relation_name.add()
method for ManyToMany
relations and reverse side of ForeignKey
relation.
sender
- sender class, instance
- instance to which related model is added, child
- model being added,
relation_name
- name of the relation to which child is added, for add signals also passed_kwargs
- dict of kwargs passed to add()
post_relation_add
post_relation_add(sender: Type["Model"], instance: "Model", child: "Model",
relation_name: str, passed_args: Dict)
Send for Model.relation_name.add()
method for ManyToMany
relations and reverse side of ForeignKey
relation.
sender
- sender class, instance
- instance to which related model is added, child
- model being added,
relation_name
- name of the relation to which child is added, for add signals also passed_kwargs
- dict of kwargs passed to add()
pre_relation_remove
pre_relation_remove(sender: Type["Model"], instance: "Model", child: "Model",
relation_name: str)
Send for Model.relation_name.remove()
method for ManyToMany
relations and reverse side of ForeignKey
relation.
sender
- sender class, instance
- instance to which related model is added, child
- model being added,
relation_name
- name of the relation to which child is added.
post_relation_remove
post_relation_remove(sender: Type["Model"], instance: "Model", child: "Model",
relation_name: str, passed_args: Dict)
Send for Model.relation_name.remove()
method for ManyToMany
relations and reverse side of ForeignKey
relation.
sender
- sender class, instance
- instance to which related model is added, child
- model being added,
relation_name
- name of the relation to which child is added.
post_bulk_update
post_bulk_update(sender: Type["Model"], instances: List["Model"], **kwargs)
,
Send for Model.objects.bulk_update(List[objects])
method.
Defining your own signals
Note that you can create your own signals although you will have to send them manually in your code or subclass ormar.Model
and trigger your signals there.
Creating new signal is super easy. Following example will set a new signal with name your_custom_signal.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 |
|
Actually under the hood signal is a SignalEmitter
instance that keeps a dictionary of know signals, and allows you
to access them as attributes. When you try to access a signal that does not exist SignalEmitter
will create one for you.
So example above can be simplified to. The Signal
will be created for you.
1 |
|
Now to trigger this signal you need to call send method of the Signal.
1 |
|
Note that sender is the only required parameter and it should be ormar Model class.
Additional parameters have to be passed as keyword arguments.
1 |
|