boardinghouse.signals module¶
Signals that are fired as part of the django-boardinghouse project.
-
boardinghouse.signals.
find_schema
¶ A mechanism for allowing an arbitrary app to respond with a schema object that satisfies the request (matching the schema value).
-
boardinghouse.signals.
schema_created
¶ Sent when a new schema object has been created in the database. Accepts a single argument, the (internal) name of the schema.
-
boardinghouse.signals.
schema_pre_activate
¶ Sent just before a schema will be activated. May be used to abort this by throwing an exception.
-
boardinghouse.signals.
schema_post_activate
¶ Sent immediately after a schema has been activated.
-
boardinghouse.signals.
session_requesting_schema_change
¶ Sent when a user-session has requested (and is, according to default rules, allowed to change to this schema). May be used to prevent the change, by throwing an exception.
-
boardinghouse.signals.
session_schema_changed
¶ Sent when a user-session has changed it’s schema.
-
boardinghouse.signals.
schema_aware_operation
¶ Sent when a migration operation that needs to be applied to each schema is due to be applied. Internally, this signal is used to ensure that the template schema and all currently existing schemata have the migration applied to them.
This is also used by the
contrib.template
app to ensure that operations are applied toboardinghouse.contrib.template.models.SchemaTemplate
instances.