diff options
| author | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2020-07-28 11:54:01 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-07-28 11:54:01 +0200 |
| commit | 02447fb133b53ec7d0ff068cc08f06fdf8817ef7 (patch) | |
| tree | 780a999da5ffacb6ec1593dca42c2961a83ce7d2 /docs | |
| parent | 628c4a26eee93417bb7161aa393dffb3f4c146b2 (diff) | |
Fixed #31835 -- Dropped support for JSONField __contains lookup on Oracle.
The current implementation works only for basic examples without
supporting nested structures and doesn't follow "the general principle
that the contained object must match the containing object as to
structure and data contents, possibly after discarding some
non-matching array elements or object key/value pairs from the
containing object".
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/db/queries.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/topics/db/queries.txt b/docs/topics/db/queries.txt index bf154b658d..793c0b48ad 100644 --- a/docs/topics/db/queries.txt +++ b/docs/topics/db/queries.txt @@ -960,6 +960,10 @@ contained in the top-level of the field. For example:: >>> Dog.objects.filter(data__contains={'breed': 'collie'}) <QuerySet [<Dog: Meg>]> +.. admonition:: Oracle + + ``contains`` is not supported on Oracle. + .. fieldlookup:: jsonfield.contained_by ``contained_by`` |