reviewers.ReviewActionReason
Model Info
Key |
Value |
---|---|
Model Name |
ReviewActionReason |
Verbose Name |
review action reason |
Verbose Name Plural |
review action reasons |
Docstring |
ReviewActionReason(id, created, modified, is_active, name, canned_response, canned_block_reason, addon_type, cinder_policy) |
Is Abstract |
False |
Is Proxy |
False |
Is Managed |
True |
Ordering |
(‘name’,) |
Permissions |
[] |
Default Permissions |
(‘add’, ‘change’, ‘delete’, ‘view’) |
Indexes |
[] |
Constraints |
[<CheckConstraint: check=(OR: (NOT (AND: (‘canned_response’, ‘’))), (NOT (AND: (‘canned_block_reason’, ‘’)))) name=’either_canned_response_or_canned_block_reason_must_be_set’>] |
Database Table |
reviewers_reviewactionreason |
Base Manager |
None |
Default Manager |
None |
File |
/data/olympia/src/olympia/reviewers/models.py |
Starting Line Number |
719 |
Method Resolution Order |
(<class ‘olympia.reviewers.models.ReviewActionReason’>, <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 |
---|---|---|---|---|
|
PositiveIntegerField |
addon_type |
integer UNSIGNED |
addon type |
|
TextField |
canned_block_reason |
longtext |
canned block reason |
|
TextField |
canned_response |
longtext |
canned response |
|
ForeignKey |
cinder_policy_id |
integer |
cinder policy |
|
DateTimeField |
created |
datetime(6) |
created |
|
AutoField |
id |
integer AUTO_INCREMENT |
ID |
|
BooleanField |
is_active |
bool |
is active |
|
DateTimeField |
modified |
datetime(6) |
modified |
|
CharField |
name |
varchar(255) |
name |
|
ManyToOneRel |
integer |
Relations
Field Name |
Field Type |
Database Column |
Database Type |
Related Model |
Related Name |
---|---|---|---|---|---|
|
ForeignKey |
cinder_policy_id |
integer |
abuse.CinderPolicy |
reviewactionreason_set |
fields_reverse_relation=[FieldReverseRelation(name=’reviewactionreason_set’, field_type=’ManyToOneRel’, field_db_type=’integer’, related_model=’activity.ReviewActionReasonLog’, field_name_on_related_model=’reason’, 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 |
---|---|---|---|---|---|
|
ManyToOneRel |
integer |
activity.ReviewActionReasonLog |
reason |
ForeignKey |
Methods
Other Methods
Method Name |
Signature |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Private Methods
Method Name |
Signature |
---|---|
|
|
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
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
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 2025-08-26 !!!