{"title":"PostgreSQL specific model fields","version":"1.10","locale":"pl","docname":"ref/contrib/postgres/fields","url":"/pl/1.10/ref/contrib/postgres/fields/","canonical":"https://djangodocs.dev/pl/1.10/ref/contrib/postgres/fields/","summary":"All of these fields are available from the django.contrib.postgres.fields module. ArrayField Link to this heading # class ArrayField ( base_field , size = None , **…","html":"

PostgreSQL specific model fieldsLink to this heading#

\n

All of these fields are available from the django.contrib.postgres.fields\nmodule.

\n
\n

ArrayFieldLink to this heading#

\n
\n
\nclass ArrayField(base_field, size=None, **options)Link to this definition#
\n

A field for storing lists of data. Most field types can be used, you simply\npass another field instance as the base_field. You may also specify a size. ArrayField can be nested to store multi-dimensional\narrays.

\n

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

\n
\n
\nbase_fieldLink to this definition#
\n

This is a required argument.

\n

Specifies the underlying data type and behavior for the array. It\nshould be an instance of a subclass of\nField. For example, it could be an\nIntegerField or a\nCharField. Most field types are permitted,\nwith the exception of those handling relational data\n(ForeignKey,\nOneToOneField and\nManyToManyField).

\n

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

\n
Code
from django.db import models\nfrom django.contrib.postgres.fields import ArrayField\n\nclass ChessBoard(models.Model):\n    board = ArrayField(\n        ArrayField(\n            models.CharField(max_length=10, blank=True),\n            size=8,\n        ),\n        size=8,\n    )\n
\n

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

\n
\n\n
\n
\nsizeLink to this definition#
\n

This is an optional argument.

\n

If passed, the array will have a maximum size as specified. This will\nbe passed to the database, although PostgreSQL at present does not\nenforce the restriction.

\n
\n\n
\n\n\n
\n

Querying ArrayFieldLink to this heading#

\n

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

\n
Code
from django.db import models\nfrom django.contrib.postgres.fields import ArrayField\n\nclass Post(models.Model):\n    name = models.CharField(max_length=200)\n    tags = ArrayField(models.CharField(max_length=200), blank=True)\n\n    def __str__(self):  # __unicode__ on Python 2\n        return self.name\n
\n
\n

containsLink to this heading#

\n

The contains lookup is overridden on ArrayField. The\nreturned objects will be those where the values passed are a subset of the\ndata. It uses the SQL operator @>. For example:

\n
Code
>>> Post.objects.create(name='First post', tags=['thoughts', 'django'])\n>>> Post.objects.create(name='Second post', tags=['thoughts'])\n>>> Post.objects.create(name='Third post', tags=['tutorial', 'django'])\n\n>>> Post.objects.filter(tags__contains=['thoughts'])\n<QuerySet [<Post: First post>, <Post: Second post>]>\n\n>>> Post.objects.filter(tags__contains=['django'])\n<QuerySet [<Post: First post>, <Post: Third post>]>\n\n>>> Post.objects.filter(tags__contains=['django', 'thoughts'])\n<QuerySet [<Post: First post>]>\n
\n
\n
\n

contained_byLink to this heading#

\n

This is the inverse of the contains lookup -\nthe objects returned will be those where the data is a subset of the values\npassed. It uses the SQL operator <@. For example:

\n
Code
>>> Post.objects.create(name='First post', tags=['thoughts', 'django'])\n>>> Post.objects.create(name='Second post', tags=['thoughts'])\n>>> Post.objects.create(name='Third post', tags=['tutorial', 'django'])\n\n>>> Post.objects.filter(tags__contained_by=['thoughts', 'django'])\n<QuerySet [<Post: First post>, <Post: Second post>]>\n\n>>> Post.objects.filter(tags__contained_by=['thoughts', 'django', 'tutorial'])\n<QuerySet [<Post: First post>, <Post: Second post>, <Post: Third post>]>\n
\n
\n
\n

overlapLink to this heading#

\n

Returns objects where the data shares any results with the values passed. Uses\nthe SQL operator &&. For example:

\n
Code
>>> Post.objects.create(name='First post', tags=['thoughts', 'django'])\n>>> Post.objects.create(name='Second post', tags=['thoughts'])\n>>> Post.objects.create(name='Third post', tags=['tutorial', 'django'])\n\n>>> Post.objects.filter(tags__overlap=['thoughts'])\n<QuerySet [<Post: First post>, <Post: Second post>]>\n\n>>> Post.objects.filter(tags__overlap=['thoughts', 'tutorial'])\n<QuerySet [<Post: First post>, <Post: Second post>, <Post: Third post>]>\n
\n
\n
\n

lenLink to this heading#

\n

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

\n
Code
>>> Post.objects.create(name='First post', tags=['thoughts', 'django'])\n>>> Post.objects.create(name='Second post', tags=['thoughts'])\n\n>>> Post.objects.filter(tags__len=1)\n<QuerySet [<Post: Second post>]>\n
\n
\n
\n

Index transformsLink to this heading#

\n

This class of transforms allows you to index into the array in queries. Any\nnon-negative integer can be used. There are no errors if it exceeds the\nsize of the array. The lookups available after the\ntransform are those from the base_field. For\nexample:

\n
Code
>>> Post.objects.create(name='First post', tags=['thoughts', 'django'])\n>>> Post.objects.create(name='Second post', tags=['thoughts'])\n\n>>> Post.objects.filter(tags__0='thoughts')\n<QuerySet [<Post: First post>, <Post: Second post>]>\n\n>>> Post.objects.filter(tags__1__iexact='Django')\n<QuerySet [<Post: First post>]>\n\n>>> Post.objects.filter(tags__276='javascript')\n<QuerySet []>\n
\n\n
\n
\n

Slice transformsLink to this heading#

\n

This class of transforms allow you to take a slice of the array. Any two\nnon-negative integers can be used, separated by a single underscore. The\nlookups available after the transform do not change. For example:

\n
Code
>>> Post.objects.create(name='First post', tags=['thoughts', 'django'])\n>>> Post.objects.create(name='Second post', tags=['thoughts'])\n>>> Post.objects.create(name='Third post', tags=['django', 'python', 'thoughts'])\n\n>>> Post.objects.filter(tags__0_1=['thoughts'])\n<QuerySet [<Post: First post>, <Post: Second post>]>\n\n>>> Post.objects.filter(tags__0_2__contains=['thoughts'])\n<QuerySet [<Post: First post>, <Post: Second post>]>\n
\n\n\n
\n
\n
\n

Indexing ArrayFieldLink to this heading#

\n

At present using db_index will create a\nbtree index. This does not offer particularly significant help to querying.\nA more useful index is a GIN index, which you should create using a\nRunSQL operation.

\n
\n
\n
\n

HStoreFieldLink to this heading#

\n
\n
\nclass HStoreField(**options)Link to this definition#
\n

A field for storing mappings of strings to strings. The Python data type\nused is a dict.

\n

To use this field, you’ll need to:

\n
    \n

  1. Add 'django.contrib.postgres' in your INSTALLED_APPS.

    2. \n

  2. Setup the hstore extension in\nPostgreSQL.

    3. \n
\n

You’ll see an error like can't adapt type 'dict' if you skip the first\nstep, or type "hstore" does not exist if you skip the second.

\n
\n\n\n
\n

Querying HStoreFieldLink to this heading#

\n

In addition to the ability to query by key, there are a number of custom\nlookups available for HStoreField.

\n

We will use the following example model:

\n
Code
from django.contrib.postgres.fields import HStoreField\nfrom django.db import models\n\nclass Dog(models.Model):\n    name = models.CharField(max_length=200)\n    data = HStoreField()\n\n    def __str__(self):  # __unicode__ on Python 2\n        return self.name\n
\n
\n

Key lookupsLink to this heading#

\n

To query based on a given key, you simply use that key as the lookup name:

\n
Code
>>> Dog.objects.create(name='Rufus', data={'breed': 'labrador'})\n>>> Dog.objects.create(name='Meg', data={'breed': 'collie'})\n\n>>> Dog.objects.filter(data__breed='collie')\n<QuerySet [<Dog: Meg>]>\n
\n

You can chain other lookups after key lookups:

\n
Code
>>> Dog.objects.filter(data__breed__contains='l')\n<QuerySet [<Dog: Rufus>, <Dog: Meg>]>\n
\n

If the key you wish to query by clashes with the name of another lookup, you\nneed to use the hstorefield.contains lookup instead.

\n\n
\n
\n

containsLink to this heading#

\n

The contains lookup is overridden on\nHStoreField. The returned objects are\nthose where the given dict of key-value pairs are all contained in the\nfield. It uses the SQL operator @>. For example:

\n
Code
>>> Dog.objects.create(name='Rufus', data={'breed': 'labrador', 'owner': 'Bob'})\n>>> Dog.objects.create(name='Meg', data={'breed': 'collie', 'owner': 'Bob'})\n>>> Dog.objects.create(name='Fred', data={})\n\n>>> Dog.objects.filter(data__contains={'owner': 'Bob'})\n<QuerySet [<Dog: Rufus>, <Dog: Meg>]>\n\n>>> Dog.objects.filter(data__contains={'breed': 'collie'})\n<QuerySet [<Dog: Meg>]>\n
\n
\n
\n

contained_byLink to this heading#

\n

This is the inverse of the contains lookup -\nthe objects returned will be those where the key-value pairs on the object are\na subset of those in the value passed. It uses the SQL operator <@. For\nexample:

\n
Code
>>> Dog.objects.create(name='Rufus', data={'breed': 'labrador', 'owner': 'Bob'})\n>>> Dog.objects.create(name='Meg', data={'breed': 'collie', 'owner': 'Bob'})\n>>> Dog.objects.create(name='Fred', data={})\n\n>>> Dog.objects.filter(data__contained_by={'breed': 'collie', 'owner': 'Bob'})\n<QuerySet [<Dog: Meg>, <Dog: Fred>]>\n\n>>> Dog.objects.filter(data__contained_by={'breed': 'collie'})\n<QuerySet [<Dog: Fred>]>\n
\n
\n
\n

has_keyLink to this heading#

\n

Returns objects where the given key is in the data. Uses the SQL operator\n?. For example:

\n
Code
>>> Dog.objects.create(name='Rufus', data={'breed': 'labrador'})\n>>> Dog.objects.create(name='Meg', data={'breed': 'collie', 'owner': 'Bob'})\n\n>>> Dog.objects.filter(data__has_key='owner')\n<QuerySet [<Dog: Meg>]>\n
\n
\n
\n

has_any_keysLink to this heading#

\n\n

Returns objects where any of the given keys are in the data. Uses the SQL\noperator ?|. For example:

\n
Code
>>> Dog.objects.create(name='Rufus', data={'breed': 'labrador'})\n>>> Dog.objects.create(name='Meg', data={'owner': 'Bob'})\n>>> Dog.objects.create(name='Fred', data={})\n\n>>> Dog.objects.filter(data__has_any_keys=['owner', 'breed'])\n<QuerySet [<Dog: Rufus>, <Dog: Meg>]>\n
\n
\n
\n

has_keysLink to this heading#

\n

Returns objects where all of the given keys are in the data. Uses the SQL operator\n?&. For example:

\n
Code
>>> Dog.objects.create(name='Rufus', data={})\n>>> Dog.objects.create(name='Meg', data={'breed': 'collie', 'owner': 'Bob'})\n\n>>> Dog.objects.filter(data__has_keys=['breed', 'owner'])\n<QuerySet [<Dog: Meg>]>\n
\n
\n
\n

keysLink to this heading#

\n

Returns objects where the array of keys is the given value. Note that the order\nis not guaranteed to be reliable, so this transform is mainly useful for using\nin conjunction with lookups on\nArrayField. Uses the SQL function\nakeys(). For example:

\n
Code
>>> Dog.objects.create(name='Rufus', data={'toy': 'bone'})\n>>> Dog.objects.create(name='Meg', data={'breed': 'collie', 'owner': 'Bob'})\n\n>>> Dog.objects.filter(data__keys__overlap=['breed', 'toy'])\n<QuerySet [<Dog: Rufus>, <Dog: Meg>]>\n
\n
\n
\n

valuesLink to this heading#

\n

Returns objects where the array of values is the given value. Note that the\norder is not guaranteed to be reliable, so this transform is mainly useful for\nusing in conjunction with lookups on\nArrayField. Uses the SQL function\navalues(). For example:

\n
Code
>>> Dog.objects.create(name='Rufus', data={'breed': 'labrador'})\n>>> Dog.objects.create(name='Meg', data={'breed': 'collie', 'owner': 'Bob'})\n\n>>> Dog.objects.filter(data__values__contains=['collie'])\n<QuerySet [<Dog: Meg>]>\n
\n
\n
\n
\n
\n

JSONFieldLink to this heading#

\n\n
\n
\nclass JSONField(**options)Link to this definition#
\n

A field for storing JSON encoded data. In Python the data is represented in\nits Python native format: dictionaries, lists, strings, numbers, booleans\nand None.

\n

If you want to store other data types, you’ll need to serialize them first.\nFor example, you might cast a datetime to a string. You might also want\nto convert the string back to a datetime when you retrieve the data\nfrom the database. There are some third-party JSONField implementations\nwhich do this sort of thing automatically.

\n

If you give the field a default, ensure\nit’s a callable such as dict (for an empty default) or a callable that\nreturns a dict (such as a function). Incorrectly using default={}\ncreates a mutable default that is shared between all instances of\nJSONField.

\n
\n\n\n
\n

Querying JSONFieldLink to this heading#

\n

We will use the following example model:

\n
Code
from django.contrib.postgres.fields import JSONField\nfrom django.db import models\n\nclass Dog(models.Model):\n    name = models.CharField(max_length=200)\n    data = JSONField()\n\n    def __str__(self):  # __unicode__ on Python 2\n        return self.name\n
\n
\n

Key, index, and path lookupsLink to this heading#

\n

To query based on a given dictionary key, simply use that key as the lookup\nname:

\n
Code
>>> Dog.objects.create(name='Rufus', data={\n...     'breed': 'labrador',\n...     'owner': {\n...         'name': 'Bob',\n...         'other_pets': [{\n...             'name': 'Fishy',\n...         }],\n...     },\n... })\n>>> Dog.objects.create(name='Meg', data={'breed': 'collie'})\n\n>>> Dog.objects.filter(data__breed='collie')\n<QuerySet [<Dog: Meg>]>\n
\n

Multiple keys can be chained together to form a path lookup:

\n
Code
>>> Dog.objects.filter(data__owner__name='Bob')\n<QuerySet [<Dog: Rufus>]>\n
\n

If the key is an integer, it will be interpreted as an index lookup in an\narray:

\n
Code
>>> Dog.objects.filter(data__owner__other_pets__0__name='Fishy')\n<QuerySet [<Dog: Rufus>]>\n
\n

If the key you wish to query by clashes with the name of another lookup, use\nthe jsonfield.contains lookup instead.

\n

If only one key or index is used, the SQL operator -> is used. If multiple\noperators are used then the #> operator is used.

\n\n
\n
\n

Containment and key operationsLink to this heading#

\n

JSONField shares lookups relating to\ncontainment and keys with HStoreField.

\n\n
\n
\n
\n
\n

Range FieldsLink to this heading#

\n

There are five range field types, corresponding to the built-in range types in\nPostgreSQL. These fields are used to store a range of values; for example the\nstart and end timestamps of an event, or the range of ages an activity is\nsuitable for.

\n

All of the range fields translate to psycopg2 Range objects in python, but also accept tuples as input if no bounds\ninformation is necessary. The default is lower bound included, upper bound\nexcluded; that is, [).

\n
\n

IntegerRangeFieldLink to this heading#

\n
\n
\nclass IntegerRangeField(**options)Link to this definition#
\n

Stores a range of integers. Based on an\nIntegerField. Represented by an int4range in\nthe database and a NumericRange in\nPython.

\n

Regardless of the bounds specified when saving the data, PostgreSQL always\nreturns a range in a canonical form that includes the lower bound and\nexcludes the upper bound; that is [).

\n
\n\n
\n
\n

BigIntegerRangeFieldLink to this heading#

\n
\n
\nclass BigIntegerRangeField(**options)Link to this definition#
\n

Stores a range of large integers. Based on a\nBigIntegerField. Represented by an int8range\nin the database and a NumericRange in\nPython.

\n

Regardless of the bounds specified when saving the data, PostgreSQL always\nreturns a range in a canonical form that includes the lower bound and\nexcludes the upper bound; that is [).

\n
\n\n
\n
\n

FloatRangeFieldLink to this heading#

\n
\n
\nclass FloatRangeField(**options)Link to this definition#
\n

Stores a range of floating point values. Based on a\nFloatField. Represented by a numrange in the\ndatabase and a NumericRange in Python.

\n
\n\n
\n
\n

DateTimeRangeFieldLink to this heading#

\n
\n
\nclass DateTimeRangeField(**options)Link to this definition#
\n

Stores a range of timestamps. Based on a\nDateTimeField. Represented by a tztsrange in\nthe database and a DateTimeTZRange in\nPython.

\n
\n\n
\n
\n

DateRangeFieldLink to this heading#

\n
\n
\nclass DateRangeField(**options)Link to this definition#
\n

Stores a range of dates. Based on a\nDateField. Represented by a daterange in the\ndatabase and a DateRange in Python.

\n

Regardless of the bounds specified when saving the data, PostgreSQL always\nreturns a range in a canonical form that includes the lower bound and\nexcludes the upper bound; that is [).

\n
\n\n
\n
\n

Querying Range FieldsLink to this heading#

\n

There are a number of custom lookups and transforms for range fields. They are\navailable on all the above fields, but we will use the following example\nmodel:

\n
Code
from django.contrib.postgres.fields import IntegerRangeField\nfrom django.db import models\n\nclass Event(models.Model):\n    name = models.CharField(max_length=200)\n    ages = IntegerRangeField()\n    start = models.DateTimeField()\n\n    def __str__(self):  # __unicode__ on Python 2\n        return self.name\n
\n

We will also use the following example objects:

\n
Code
>>> import datetime\n>>> from django.utils import timezone\n>>> now = timezone.now()\n>>> Event.objects.create(name='Soft play', ages=(0, 10), start=now)\n>>> Event.objects.create(name='Pub trip', ages=(21, None), start=now - datetime.timedelta(days=1))\n
\n

and NumericRange:

\n
Code
>>> from psycopg2.extras import NumericRange\n
\n
\n

Containment functionsLink to this heading#

\n

As with other PostgreSQL fields, there are three standard containment\noperators: contains, contained_by and overlap, using the SQL\noperators @>, <@, and && respectively.

\n
\n
containsLink to this heading#
\n
Code
>>> Event.objects.filter(ages__contains=NumericRange(4, 5))\n<QuerySet [<Event: Soft play>]>\n
\n
\n
\n
contained_byLink to this heading#
\n
Code
>>> Event.objects.filter(ages__contained_by=NumericRange(0, 15))\n<QuerySet [<Event: Soft play>]>\n
\n\n

The contained_by lookup is also available on the non-range field types:\nIntegerField,\nBigIntegerField,\nFloatField, DateField,\nand DateTimeField. For example:

\n
Code
>>> from psycopg2.extras import DateTimeTZRange\n>>> Event.objects.filter(start__contained_by=DateTimeTZRange(\n...     timezone.now() - datetime.timedelta(hours=1),\n...     timezone.now() + datetime.timedelta(hours=1),\n... )\n<QuerySet [<Event: Soft play>]>\n
\n
\n
\n
overlapLink to this heading#
\n
Code
>>> Event.objects.filter(ages__overlap=NumericRange(8, 12))\n<QuerySet [<Event: Soft play>]>\n
\n
\n
\n
\n

Comparison functionsLink to this heading#

\n

Range fields support the standard lookups: lt, gt,\nlte and gte. These are not particularly helpful - they\ncompare the lower bounds first and then the upper bounds only if necessary.\nThis is also the strategy used to order by a range field. It is better to use\nthe specific range comparison operators.

\n
\n
fully_ltLink to this heading#
\n

The returned ranges are strictly less than the passed range. In other words,\nall the points in the returned range are less than all those in the passed\nrange.

\n
Code
>>> Event.objects.filter(ages__fully_lt=NumericRange(11, 15))\n<QuerySet [<Event: Soft play>]>\n
\n
\n
\n
fully_gtLink to this heading#
\n

The returned ranges are strictly greater than the passed range. In other words,\nthe all the points in the returned range are greater than all those in the\npassed range.

\n
Code
>>> Event.objects.filter(ages__fully_gt=NumericRange(11, 15))\n<QuerySet [<Event: Pub trip>]>\n
\n
\n
\n
not_ltLink to this heading#
\n

The returned ranges do not contain any points less than the passed range, that\nis the lower bound of the returned range is at least the lower bound of the\npassed range.

\n
Code
>>> Event.objects.filter(ages__not_lt=NumericRange(0, 15))\n<QuerySet [<Event: Soft play>, <Event: Pub trip>]>\n
\n
\n
\n
not_gtLink to this heading#
\n

The returned ranges do not contain any points greater than the passed range, that\nis the upper bound of the returned range is at most the upper bound of the\npassed range.

\n
Code
>>> Event.objects.filter(ages__not_gt=NumericRange(3, 10))\n<QuerySet [<Event: Soft play>]>\n
\n
\n
\n
adjacent_toLink to this heading#
\n

The returned ranges share a bound with the passed range.

\n
Code
>>> Event.objects.filter(ages__adjacent_to=NumericRange(10, 21))\n<QuerySet [<Event: Soft play>, <Event: Pub trip>]>\n
\n
\n
\n
\n

Querying using the boundsLink to this heading#

\n

There are three transforms available for use in queries. You can extract the\nlower or upper bound, or query based on emptiness.

\n
\n
startswithLink to this heading#
\n

Returned objects have the given lower bound. Can be chained to valid lookups\nfor the base field.

\n
Code
>>> Event.objects.filter(ages__startswith=21)\n<QuerySet [<Event: Pub trip>]>\n
\n
\n
\n
endswithLink to this heading#
\n

Returned objects have the given upper bound. Can be chained to valid lookups\nfor the base field.

\n
Code
>>> Event.objects.filter(ages__endswith=10)\n<QuerySet [<Event: Soft play>]>\n
\n
\n
\n
isemptyLink to this heading#
\n

Returned objects are empty ranges. Can be chained to valid lookups for a\nBooleanField.

\n
Code
>>> Event.objects.filter(ages__isempty=True)\n<QuerySet []>\n
\n
\n
\n
\n

Defining your own range typesLink to this heading#

\n

PostgreSQL allows the definition of custom range types. Django’s model and form\nfield implementations use base classes below, and psycopg2 provides a\nregister_range() to allow use of custom range\ntypes.

\n
\n
\nclass RangeField(**options)Link to this definition#
\n

Base class for model range fields.

\n
\n
\nbase_fieldLink to this definition#
\n

The model field class to use.

\n
\n\n
\n
\nrange_typeLink to this definition#
\n

The psycopg2 range type to use.

\n
\n\n
\n
\nform_fieldLink to this definition#
\n

The form field class to use. Should be a subclass of\ndjango.contrib.postgres.forms.BaseRangeField.

\n
\n\n
\n\n
\n
\nclass django.contrib.postgres.forms.BaseRangeFieldLink to this definition#
\n

Base class for form range fields.

\n
\n
\nbase_fieldLink to this definition#
\n

The form field to use.

\n
\n\n
\n
\nrange_typeLink to this definition#
\n

The psycopg2 range type to use.

\n
\n\n
\n\n
\n
\n
","rootId":"postgresql-specific-model-fields","toc":[{"title":"ArrayField","anchor":"arrayfield","children":[{"title":"Querying ArrayField","anchor":"querying-arrayfield","children":[{"title":"contains","anchor":"contains","children":[]},{"title":"contained_by","anchor":"contained-by","children":[]},{"title":"overlap","anchor":"overlap","children":[]},{"title":"len","anchor":"len","children":[]},{"title":"Index transforms","anchor":"index-transforms","children":[]},{"title":"Slice transforms","anchor":"slice-transforms","children":[]}]},{"title":"Indexing ArrayField","anchor":"indexing-arrayfield","children":[]}]},{"title":"HStoreField","anchor":"hstorefield","children":[{"title":"Querying HStoreField","anchor":"querying-hstorefield","children":[{"title":"Key lookups","anchor":"key-lookups","children":[]},{"title":"contains","anchor":"std-fieldlookup-hstorefield.contains","children":[]},{"title":"contained_by","anchor":"std-fieldlookup-hstorefield.contained_by","children":[]},{"title":"has_key","anchor":"has-key","children":[]},{"title":"has_any_keys","anchor":"has-any-keys","children":[]},{"title":"has_keys","anchor":"has-keys","children":[]},{"title":"keys","anchor":"keys","children":[]},{"title":"values","anchor":"values","children":[]}]}]},{"title":"JSONField","anchor":"jsonfield","children":[{"title":"Querying JSONField","anchor":"querying-jsonfield","children":[{"title":"Key, index, and path lookups","anchor":"key-index-and-path-lookups","children":[]},{"title":"Containment and key operations","anchor":"containment-and-key-operations","children":[]}]}]},{"title":"Range Fields","anchor":"range-fields","children":[{"title":"IntegerRangeField","anchor":"integerrangefield","children":[]},{"title":"BigIntegerRangeField","anchor":"bigintegerrangefield","children":[]},{"title":"FloatRangeField","anchor":"floatrangefield","children":[]},{"title":"DateTimeRangeField","anchor":"datetimerangefield","children":[]},{"title":"DateRangeField","anchor":"daterangefield","children":[]},{"title":"Querying Range Fields","anchor":"querying-range-fields","children":[{"title":"Containment functions","anchor":"containment-functions","children":[{"title":"contains","anchor":"std-fieldlookup-rangefield.contains","children":[]},{"title":"contained_by","anchor":"std-fieldlookup-rangefield.contained_by","children":[]},{"title":"overlap","anchor":"std-fieldlookup-rangefield.overlap","children":[]}]},{"title":"Comparison functions","anchor":"comparison-functions","children":[{"title":"fully_lt","anchor":"fully-lt","children":[]},{"title":"fully_gt","anchor":"fully-gt","children":[]},{"title":"not_lt","anchor":"not-lt","children":[]},{"title":"not_gt","anchor":"not-gt","children":[]},{"title":"adjacent_to","anchor":"adjacent-to","children":[]}]},{"title":"Querying using the bounds","anchor":"querying-using-the-bounds","children":[{"title":"startswith","anchor":"startswith","children":[]},{"title":"endswith","anchor":"endswith","children":[]},{"title":"isempty","anchor":"isempty","children":[]}]},{"title":"Defining your own range types","anchor":"defining-your-own-range-types","children":[]}]}]}],"breadcrumbs":[{"docname":"ref/index","title":"API Reference","url":"/pl/1.10/ref/"},{"docname":"ref/contrib/index","title":"contrib packages","url":"/pl/1.10/ref/contrib/"},{"docname":"ref/contrib/postgres/index","title":"django.contrib.postgres","url":"/pl/1.10/ref/contrib/postgres/"}],"prev":{"docname":"ref/contrib/postgres/aggregates","title":"PostgreSQL specific aggregation functions","url":"/pl/1.10/ref/contrib/postgres/aggregates/"},"next":{"docname":"ref/contrib/postgres/forms","title":"PostgreSQL specific form fields and widgets","url":"/pl/1.10/ref/contrib/postgres/forms/"},"formats":{"html":"/pl/1.10/ref/contrib/postgres/fields/","markdown":"/pl/1.10/ref/contrib/postgres/fields.md","json":"/pl/1.10/ref/contrib/postgres/fields.json"},"source":"https://github.com/django/django/blob/stable/1.10.x/docs/ref/contrib/postgres/fields.txt","official":"https://docs.djangoproject.com/pl/1.10/ref/contrib/postgres/fields/","inVersions":["6.1","6.0","5.2","5.1","5.0","4.2","4.1","4.0","3.2","3.1","3.0","2.2","2.1","2.0","1.11","1.10"],"inLocales":["en","fr","ja","id","pt-br","es","el","pl"]}