scanners.ScannerWebhookEvent

Model Info

Key	Value
Model Name	ScannerWebhookEvent
Verbose Name	scanner webhook event
Verbose Name Plural	scanner webhook events
Docstring	ScannerWebhookEvent(id, created, modified, webhook, event)
Is Abstract	False
Is Proxy	False
Is Managed	True
Ordering	[]
Permissions	[]
Default Permissions	(‘add’, ‘change’, ‘delete’, ‘view’)
Indexes	[]
Constraints	[]
Database Table	scanners_webhook_events
Base Manager	None
Default Manager	None
File	/data/olympia/src/olympia/scanners/models.py
Starting Line Number	284
Method Resolution Order	(<class ‘olympia.scanners.models.ScannerWebhookEvent’>, <class ‘olympia.amo.models.ModelBase’>, <class ‘olympia.amo.models.SaveUpdateMixin’>, <class ‘django.db.models.base.Model’>, <class ‘django.db.models.utils.AltersData’>, <class ‘object’>)

Fields

Field Name	Field Type	Database Column	Database Type	Verbose Name
created	DateTimeField	created	datetime(6)	created
event	PositiveSmallIntegerField	event	smallint UNSIGNED	event
id (pk)	AutoField	id	integer AUTO_INCREMENT	ID
modified	DateTimeField	modified	datetime(6)	modified
scannerresults	ManyToOneRel		integer
webhook	ForeignKey	webhook_id	integer	webhook

Relations

Field Name	Field Type	Database Column	Database Type	Related Model	Related Name
webhook	ForeignKey	webhook_id	integer	scanners.ScannerWebhook	scannerwebhookevent_set

fields_reverse_relation=[FieldReverseRelation(name=’scannerresults’, field_type=’ManyToOneRel’, field_db_type=’integer’, related_model=’scanners.ScannerResult’, field_name_on_related_model=’webhook_event’, field_type_on_related_model=’ForeignKey’)]

Reverse Relations

Field Name	Field Type	Database Type	Related Model	Field Name on Related Model	Field Type on Related Model
scannerresults	ManyToOneRel	integer	scanners.ScannerResult	webhook_event	ForeignKey

Methods

Other Methods

Method Name	Signature
get_admin_absolute_url	(self)
get_admin_url_path	(self)
get_event_display	(self, *, field=<django.db.models.fields.PositiveSmallIntegerField: event>)
get_next_by_created	(self, *, field=<django.db.models.fields.DateTimeField: created>, is_next=True, **kwargs)
get_next_by_modified	(self, *, field=<django.db.models.fields.DateTimeField: modified>, is_next=True, **kwargs)
get_previous_by_created	(self, *, field=<django.db.models.fields.DateTimeField: created>, is_next=False, **kwargs)
get_previous_by_modified	(self, *, field=<django.db.models.fields.DateTimeField: modified>, is_next=False, **kwargs)
get_unfiltered_manager	()
reload	(self)
serializable_reference	(self)
update	(self, **kw)

Private Methods

Method Name	Signature
_get_field_value_map	(self, meta, exclude=None)

Custom Managers

default

Class: ManagerBase

*Base for all managers in AMO.

Returns BaseQuerySets.

If a model has translated fields, they’ll be attached through a transform function.*

Custom Methods

transform(self, fn)

Custom QuerySet

Class: BaseQuerySet

Represent a lazy database lookup for a set of objects.

Custom Methods

get_with_primary_fallback(self, *args, **kwargs)

*Like get(), but if using a non-default database and DoesNotExist is raised, another attempt is made using the default database instead.

Intended to be used in places where replication lag could cause the object not to exist for a brief moment and forcing use of primary db at all times is undesirable.*

no_transforms(self)

only_translations(self)

Remove all transforms except translations.

optimized_count(self)

*Slightly optimized count() for cases where there is a DISTINCT in the queryset.

When a count() call is made on a queryset that has a distinct, that causes django to run the full SELECT (including all fields, distinct, ordering etc) in a subquery and then COUNT() on the result of that subquery, which is costly/innefficient. That’s tracked in https://code.djangoproject.com/ticket/30685. We can’t easily fix the fact that there is a subquery, but we can avoid selecting all fields and ordering in that subquery needlessly.*

pop_transforms(self)

transform(self, fn)

objects

Class: ManagerBase

*Base for all managers in AMO.

Returns BaseQuerySets.

If a model has translated fields, they’ll be attached through a transform function.*

Custom Methods

transform(self, fn)

Custom QuerySet

Class: BaseQuerySet

Represent a lazy database lookup for a set of objects.

Custom Methods

get_with_primary_fallback(self, *args, **kwargs)

*Like get(), but if using a non-default database and DoesNotExist is raised, another attempt is made using the default database instead.

Intended to be used in places where replication lag could cause the object not to exist for a brief moment and forcing use of primary db at all times is undesirable.*

no_transforms(self)

only_translations(self)

Remove all transforms except translations.

optimized_count(self)

*Slightly optimized count() for cases where there is a DISTINCT in the queryset.

When a count() call is made on a queryset that has a distinct, that causes django to run the full SELECT (including all fields, distinct, ordering etc) in a subquery and then COUNT() on the result of that subquery, which is costly/innefficient. That’s tracked in https://code.djangoproject.com/ticket/30685. We can’t easily fix the fact that there is a subquery, but we can avoid selecting all fields and ordering in that subquery needlessly.*

pop_transforms(self)

transform(self, fn)

---

!!! THIS DOCUMENT WAS AUTOGENERATED ON 2026-01-28 !!!