users.BannedUserContent

Model Info

Key	Value
Model Name	BannedUserContent
Verbose Name	banned user content
Verbose Name Plural	banned user contents
Docstring	Link between a user and the content that was disabled when they were banned. That link should be removed if the user is unbanned, and the content re-enabled.
Is Abstract	False
Is Proxy	False
Is Managed	True
Ordering	[]
Permissions	[]
Default Permissions	(‘add’, ‘change’, ‘delete’, ‘view’)
Indexes	[]
Constraints	[]
Database Table	users_bannedusercontent
Base Manager	objects
Default Manager	None
File	/data/olympia/src/olympia/users/models.py
Starting Line Number	1437
Method Resolution Order	(<class ‘olympia.users.models.BannedUserContent’>, <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
BannedUserContent_addons+	ManyToOneRel		integer
BannedUserContent_addons_users+	ManyToOneRel		integer
BannedUserContent_collections+	ManyToOneRel		integer
BannedUserContent_ratings+	ManyToOneRel		integer
addons	ManyToManyField	addons	through users.BannedUserContent_addons	addons
addons_users	ManyToManyField	addons_users	through users.BannedUserContent_addons_users	addons users
collections	ManyToManyField	collections	through users.BannedUserContent_collections	collections
created	DateTimeField	created	datetime(6)	created
modified	DateTimeField	modified	datetime(6)	modified
picture_backup_name	CharField	picture_backup_name	varchar(75)	picture backup name
picture_type	CharField	picture_type	varchar(75)	picture type
ratings	ManyToManyField	ratings	through users.BannedUserContent_ratings	ratings
user (pk)	OneToOneField	user_id	integer	user

Relations

Field Name	Field Type	Database Column	Database Type	Related Model	Related Name
addons	ManyToManyField	addons	through users.BannedUserContent_addons	addons.Addon	bannedusercontent_set
addons_users	ManyToManyField	addons_users	through users.BannedUserContent_addons_users	addons.AddonUser	bannedusercontent_set
collections	ManyToManyField	collections	through users.BannedUserContent_collections	bandwagon.Collection	bannedusercontent_set
ratings	ManyToManyField	ratings	through users.BannedUserContent_ratings	ratings.Rating	bannedusercontent_set
user (pk)	OneToOneField	user_id	integer	users.UserProfile	content_disabled_on_ban

fields_reverse_relation=[FieldReverseRelation(name=’BannedUserContent_collections+ (no reverse relation allowed)’, field_type=’ManyToOneRel’, field_db_type=’integer’, related_model=’users.BannedUserContent_collections’, field_name_on_related_model=’bannedusercontent’, field_type_on_related_model=’ForeignKey’), FieldReverseRelation(name=’BannedUserContent_addons+ (no reverse relation allowed)’, field_type=’ManyToOneRel’, field_db_type=’integer’, related_model=’users.BannedUserContent_addons’, field_name_on_related_model=’bannedusercontent’, field_type_on_related_model=’ForeignKey’), FieldReverseRelation(name=’BannedUserContent_addons_users+ (no reverse relation allowed)’, field_type=’ManyToOneRel’, field_db_type=’integer’, related_model=’users.BannedUserContent_addons_users’, field_name_on_related_model=’bannedusercontent’, field_type_on_related_model=’ForeignKey’), FieldReverseRelation(name=’BannedUserContent_ratings+ (no reverse relation allowed)’, field_type=’ManyToOneRel’, field_db_type=’integer’, related_model=’users.BannedUserContent_ratings’, field_name_on_related_model=’bannedusercontent’, 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
BannedUserContent_addons+ (no reverse relation allowed)	ManyToOneRel	integer	users.BannedUserContent_addons	bannedusercontent	ForeignKey
BannedUserContent_addons_users+ (no reverse relation allowed)	ManyToOneRel	integer	users.BannedUserContent_addons_users	bannedusercontent	ForeignKey
BannedUserContent_collections+ (no reverse relation allowed)	ManyToOneRel	integer	users.BannedUserContent_collections	bannedusercontent	ForeignKey
BannedUserContent_ratings+ (no reverse relation allowed)	ManyToOneRel	integer	users.BannedUserContent_ratings	bannedusercontent	ForeignKey

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_unfiltered_manager	()
reload	(self)
restore	(self)
restore_picture	(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 2025-10-07 !!!