users.UserRestrictionHistory

Model Info

Key	Value
Model Name	UserRestrictionHistory
Verbose Name	user restriction history
Verbose Name Plural	User Restriction History
Docstring	UserRestrictionHistory(id, created, modified, user, restriction, ip_address, last_login_ip)
Is Abstract	False
Is Proxy	False
Is Managed	True
Ordering	[]
Permissions	[]
Default Permissions	(‘add’, ‘change’, ‘delete’, ‘view’)
Indexes	[<LongNameIndex: fields=[‘ip_address’] name=’users_userrestrictionhistory_ip_address_4376df32’>, <LongNameIndex: fields=[‘last_login_ip’] name=’users_userrestrictionhistory_last_login_ip_d58d95ff’>]
Constraints	[]
Database Table	users_userrestrictionhistory
Base Manager	None
Default Manager	None
File	/data/olympia/src/olympia/users/models.py
Starting Line Number	1243
Method Resolution Order	(<class ‘olympia.users.models.UserRestrictionHistory’>, <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
id (pk)	AutoField	id	integer AUTO_INCREMENT	ID
ip_address	CharField	ip_address	varchar(45)	ip address
last_login_ip	CharField	last_login_ip	varchar(45)	last login ip
modified	DateTimeField	modified	datetime(6)	modified
restriction	PositiveSmallIntegerField	restriction	smallint UNSIGNED	restriction
user	ForeignKey	user_id	integer	user

Relations

Field Name	Field Type	Database Column	Database Type	Related Model	Related Name
user	ForeignKey	user_id	integer	users.UserProfile	restriction_history

fields_reverse_relation=[]

Methods

Other Methods

Method Name	Signature
get_admin_absolute_url	(self)
get_admin_url_path	(self)
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_restriction_display	(self, *, field=<django.db.models.fields.PositiveSmallIntegerField: restriction>)
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

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-07-09 !!!