Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://django-mongodb-backend.readthedocs.io/en/latest/ref/models/fields/ below:

Model field reference — Django MongoDB Backend 5.2.0b3.dev0 documentation

All of Django’s model fields are supported, except:

• AutoField (including BigAutoField and SmallAutoField)

• CompositePrimaryKey

• GeneratedField

A few notes about some of the other fields:

• DateTimeField is limited to millisecond precision (rather than microsecond like most other databases), and correspondingly, DurationField stores milliseconds rather than microseconds.

• SmallIntegerField and PositiveSmallIntegerField support 32 bit values (ranges (-2147483648, 2147483647) and (0, 2147483647), respectively), validated by forms and model validation. Be careful because MongoDB doesn’t prohibit inserting values outside of the supported range and unique constraints don’t work for values outside of the 32-bit range of the BSON int type.

• IntegerField, BigIntegerField and PositiveSmallIntegerField, and PositiveBigIntegerField support 64 bit values (ranges (-9223372036854775808, 9223372036854775807) and (0, 9223372036854775807), respectively), validated by forms and model validation. If you’re inserting data outside of the ORM, you must cast all values to bson.int64.Int64, otherwise values less then 32 bits will be stored as int and won’t be validated by unique constraints.

• Similarly, all DurationField values are stored as bson.int64.Int64.

Some MongoDB-specific fields are available in django_mongodb_backend.fields.

class ArrayField(base_field, max_size=None, size=None, **options)¶

A field for storing lists of data. Most field types can be used, and you pass another field instance as the base_field. You may also specify a size or max_size. ArrayField can be nested to store multi-dimensional arrays.

If you give the field a default, ensure it’s a callable such as list (for an empty default) or a callable that returns a list (such as a function). Incorrectly using default=[] creates a mutable default that is shared between all instances of ArrayField.

base_field¶

This is a required argument.

Specifies the underlying data type and behavior for the array. It should be an instance of a subclass of Field. For example, it could be an IntegerField or a CharField. Most field types are permitted, with the exception of those handling relational data (ForeignKey, OneToOneField and ManyToManyField) and file fields ( FileField and ImageField). For EmbeddedModelField, use EmbeddedModelArrayField.

It is possible to nest array fields - you can specify an instance of ArrayField as the base_field. For example:

from django.db import models
from django_mongodb_backend.fields import ArrayField


class ChessBoard(models.Model):
    board = ArrayField(
        ArrayField(
            models.CharField(max_length=10, blank=True),
            size=8,
        ),
        size=8,
    )

Transformation of values between the database and the model, validation of data and configuration, and serialization are all delegated to the underlying base field.

max_size¶

This is an optional argument.

If passed, the array will have a maximum size as specified, validated by forms and model validation, but not enforced by the database.

The max_size and size options are mutually exclusive.

size¶

This is an optional argument.

If passed, the array will have size as specified, validated by forms and model validation, but not enforced by the database.

There are a number of custom lookups and transforms for ArrayField. We will use the following example model:

from django.db import models
from django_mongodb_backend.fields import ArrayField


class Post(models.Model):
    name = models.CharField(max_length=200)
    tags = ArrayField(models.CharField(max_length=200), blank=True)

    def __str__(self):
        return self.name

The contains lookup is overridden on ArrayField. The returned objects will be those where the values passed are a subset of the data. It uses the $setIntersection operator. For example:

>>> Post.objects.create(name="First post", tags=["thoughts", "django"])
>>> Post.objects.create(name="Second post", tags=["thoughts"])
>>> Post.objects.create(name="Third post", tags=["tutorial", "django"])

>>> Post.objects.filter(tags__contains=["thoughts"])
<QuerySet [<Post: First post>, <Post: Second post>]>

>>> Post.objects.filter(tags__contains=["django"])
<QuerySet [<Post: First post>, <Post: Third post>]>

>>> Post.objects.filter(tags__contains=["django", "thoughts"])
<QuerySet [<Post: First post>]>

This is the inverse of the contains lookup - the objects returned will be those where the data is a subset of the values passed. It uses the $setIntersection operator. For example:

>>> Post.objects.create(name="First post", tags=["thoughts", "django"])
>>> Post.objects.create(name="Second post", tags=["thoughts"])
>>> Post.objects.create(name="Third post", tags=["tutorial", "django"])

>>> Post.objects.filter(tags__contained_by=["thoughts", "django"])
<QuerySet [<Post: First post>, <Post: Second post>]>

>>> Post.objects.filter(tags__contained_by=["thoughts", "django", "tutorial"])
<QuerySet [<Post: First post>, <Post: Second post>, <Post: Third post>]>

Returns objects where the data shares any results with the values passed. It uses the $setIntersection operator. For example:

>>> Post.objects.create(name="First post", tags=["thoughts", "django"])
>>> Post.objects.create(name="Second post", tags=["thoughts", "tutorial"])
>>> Post.objects.create(name="Third post", tags=["tutorial", "django"])

>>> Post.objects.filter(tags__overlap=["thoughts"])
<QuerySet [<Post: First post>, <Post: Second post>]>

>>> Post.objects.filter(tags__overlap=["thoughts", "tutorial"])
<QuerySet [<Post: First post>, <Post: Second post>, <Post: Third post>]>

Returns the length of the array. The lookups available afterward are those available for IntegerField. For example:

>>> Post.objects.create(name="First post", tags=["thoughts", "django"])
>>> Post.objects.create(name="Second post", tags=["thoughts"])

>>> Post.objects.filter(tags__len=1)
<QuerySet [<Post: Second post>]>

Index transforms index into the array. Any non-negative integer can be used. There are no errors if it exceeds the max_size of the array. The lookups available after the transform are those from the base_field. For example:

>>> Post.objects.create(name="First post", tags=["thoughts", "django"])
>>> Post.objects.create(name="Second post", tags=["thoughts"])

>>> Post.objects.filter(tags__0="thoughts")
<QuerySet [<Post: First post>, <Post: Second post>]>

>>> Post.objects.filter(tags__1__iexact="Django")
<QuerySet [<Post: First post>]>

>>> Post.objects.filter(tags__276="javascript")
<QuerySet []>

These indexes use 0-based indexing.

Slice transforms take a slice of the array. Any two non-negative integers can be used, separated by a single underscore. The lookups available after the transform do not change. For example:

>>> Post.objects.create(name="First post", tags=["thoughts", "django"])
>>> Post.objects.create(name="Second post", tags=["thoughts"])
>>> Post.objects.create(name="Third post", tags=["django", "python", "thoughts"])

>>> Post.objects.filter(tags__0_1=["thoughts"])
<QuerySet [<Post: First post>, <Post: Second post>]>

>>> Post.objects.filter(tags__0_2__contains=["thoughts"])
<QuerySet [<Post: First post>, <Post: Second post>]>

These indexes use 0-based indexing.

class EmbeddedModelField(embedded_model, **kwargs)¶

Stores a model of type embedded_model.

embedded_model¶

This is a required argument.

Specifies the model class to embed. It must be a subclass of django_mongodb_backend.models.EmbeddedModel.

It can be either a concrete model class or a lazy reference to a model class.

The embedded model cannot have relational fields (ForeignKey, OneToOneField and ManyToManyField).

It is possible to nest embedded models. For example:

from django.db import models
from django_mongodb_backend.fields import EmbeddedModelField
from django_mongodb_backend.models import EmbeddedModel

class Address(EmbeddedModel):
    ...

class Author(EmbeddedModel):
    address = EmbeddedModelField(Address)

class Book(models.Model):
    author = EmbeddedModelField(Author)

See the embedded model topic guide for more details and examples.

Migrations support is limited

makemigrations does not yet detect changes to embedded models.

After you create a model with an EmbeddedModelField or add an EmbeddedModelField to an existing model, no further updates to the embedded model will be made. Using the models above as an example, if you created these models and then added an indexed field to Address, the index created in the nested Book embed is not created.

class EmbeddedModelArrayField(embedded_model, max_size=None, **kwargs)¶

Added in version 5.2.0b1.

Similar to EmbeddedModelField, but stores a list of models of type embedded_model rather than a single instance.

embedded_model¶

This is a required argument that works just like EmbeddedModelField.embedded_model.

max_size¶

This is an optional argument.

If passed, the list will have a maximum size as specified, validated by forms and model validation, but not enforced by the database.

See the embedded model topic guide for more details and examples.

class ObjectIdAutoField¶

This field is typically the default primary key field for all models stored in MongoDB. See Specifying the default primary key field.

class ObjectIdField¶

Stores an ObjectId.

class PolymorphicEmbeddedModelField(embedded_models, **kwargs)¶

Added in version 5.2.0b2.

Stores a model of one of the types in embedded_models.

embedded_models¶

This is a required argument that specifies a list of model classes that may be embedded.

Each model class reference works just like EmbeddedModelField.embedded_model.

See the embedded model topic guide for more details and examples.

Migrations support is limited

makemigrations does not yet detect changes to embedded models, nor does it create indexes or constraints for embedded models referenced by PolymorphicEmbeddedModelField.

Forms are not supported

PolymorphicEmbeddedModelFields don’t appear in model forms.

class PolymorphicEmbeddedModelArrayField(embedded_models, **kwargs)¶

Added in version 5.2.0b2.

Similar to PolymorphicEmbeddedModelField, but stores a list of models of type embedded_models rather than a single instance.

embedded_models¶

This is a required argument that works just like PolymorphicEmbeddedModelField.embedded_models.

max_size¶

This is an optional argument.

If passed, the list will have a maximum size as specified, validated by forms and model validation, but not enforced by the database.

See the embedded model topic guide for more details and examples.

Migrations support is limited

makemigrations does not yet detect changes to embedded models, nor does it create indexes or constraints for embedded models referenced by PolymorphicEmbeddedModelArrayField.

Forms are not supported

PolymorphicEmbeddedModelArrayFields don’t appear in model forms.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4