Skip to content

Latest commit

 

History

History
62 lines (36 loc) · 2.49 KB

event.rst

File metadata and controls

62 lines (36 loc) · 2.49 KB

Event

SQLAlchemy features an ORM event API but one thing that is lacking is a way to register event handlers in a declarative way inside the Model's class definition. To bridge this gap, this module contains a collection of decorators that enable this kind of functionality.

Instead of having to write event registration like this:

from sqlalchemy import event

from myproject import Model


class User(Model):
    _id = Column(types.Integer(), primary_key=True)
    email = Column(types.String())


def set_email_listener(target, value, oldvalue, initiator):
    print("received 'set' event for target: {0}".format(target))
    return value


def before_insert_listener(mapper, connection, target):
    print("received 'before_insert' event for target: {0}".format(target))


event.listen(User.email, "set", set_email_listener, retval=True)
event.listen(User, "before_insert", before_insert_listener)

Model Events allows one to write event registration more succinctly as:

from sqlservice import event

from myproject import Model


class User(Model):
    _id = Column(types.Integer(), primary_key=True)
    email = Column(types.String())

    @event.on_set("email", retval=True)
    def on_set_email(self, value, oldvalue):
        print("received set event for target: {0}".format(target))
        return value

    @event.before_insert()
    def before_insert(self, connection, mapper):
        print("received 'before_insert' event for target: {0}".format(target))

You'll notice that in the on_set_email method, there are only 3 arguments while the same function in the sqlalchemy.event example's has 4 arguments. The sqlservice event decorators will inspect the method signatures of each event handler and only pass in the number of arguments that are defined. This way arguments that aren't used don't need to be defined.

You'll also notice that in the before_insert method, the order of the arguments is different than what's in the sqlalchemy.event example; the mapper argument is last instead of of first. This reordering of arguments was done so that the class methods can be defined with the self argument as the first argument.

For details on each event type's expected function signature, see SQLAlchemy's ORM Events.

For a full listing of sqlservice event decorators, see the :mod:`sqlservice.event`.