Re: [Django] #31839: Add additional database functions.

[Django]

#31839: Add additional database functions.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  functions, random,   | Triage Stage:
  truncate, log2, log10, bit |  Unreviewed
  length, octet length, hyperbolic   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by felixxm):

 I'm not sure if it's worth adding extra database functions:

 -  `Log2` and `Log10` can be achieved with proving base to `Log` so I'm
 against them,
 - hyperbolic functions are supported only on PostgreSQL 12+, we need to
 emulate them on other DBs, it's not worth, IMO,
 - `BitLength` and `OctetLength` will probably not work on Oracle.


 `Truncate` and `Round` sound reasonable.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.39d168e717c28f54578cf860320f1869%40djangoproject.com.

Re: [Django] #31837: Possible manager migration bug

[Django]

#31837: Possible manager migration bug
+--
 Reporter:  Gordon Wrigley  |Owner:  nobody
 Type:  Uncategorized   |   Status:  closed
Component:  Migrations  |  Version:  3.0
 Severity:  Normal  |   Resolution:  invalid
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by felixxm):

 * status:  new => closed
 * resolution:   => invalid
 * component:  Uncategorized => Migrations


Comment:

 Thanks for this report, IMO this is not a bug. You should define
 `use_in_migrations = True` on the custom manager class for `objects` (see
 #26643) and [https://docs.djangoproject.com/en/3.0/topics/migrations
 /#model-managers "Model managers" docs].

 Closing per TicketClosingReasons/UseSupportChannels.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.7a3d8d35c656d8c6e9e0a36092d8d1db%40djangoproject.com.

Re: [Django] #31838: django.contrib.gis.geos.error.GEOSException: Could not parse version info string "3.8.0-CAPI-1.13.1 "

[Django]

#31838: django.contrib.gis.geos.error.GEOSException: Could not parse version 
info
string "3.8.0-CAPI-1.13.1 "
---+--
 Reporter:  palewire   |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Uncategorized  |  Version:
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Simon Charette):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Both Django 1.11.x and Python 2.7 reached their end of life at this point.

 You should upgrade to supported Python and Django stack.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.419fcc7dabfdf17f32e8ed118461ab75%40djangoproject.com.

Re: [Django] #31839: Add additional database functions.

[Django]

#31839: Add additional database functions.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  functions, random,   | Triage Stage:
  truncate, log2, log10, bit |  Unreviewed
  length, octet length, hyperbolic   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nick Pope):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/13252 PR]

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.a398cd32a0c315e8c3a6c179078cf1e1%40djangoproject.com.

[Django] #31839: Add additional database functions.

[Django]

#31839: Add additional database functions.
-+-
   Reporter:  Nick Pope  |  Owner:  Nick Pope
   Type:  New| Status:  assigned
  feature|
  Component:  Database   |Version:  master
  layer (models, ORM)|   Keywords:  functions, random,
   Severity:  Normal |  truncate, log2, log10, bit length,
   Triage Stage: |  octet length, hyperbolic
  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I propose adding some additional database functions:

 - `Random`  -- generate random numbers in the range `[0.0, 0.1)`.
 - `Truncate` -- round number towards zero. (SQL function is `TRUNC`, but
 `Trunc` is used for date truncation in Django.)
 - `Log2` and `Log10` -- simple logarithm functions without needing to
 provide the base.
 - `ACosh`, `ASinh`, `ATanh`, `Cosh`, `Sinh`, and `Tanh` -- hyperbolic
 functions.
 - `BitLength` and `OctetLength` -- length of string in bits and bytes,
 complement to `Length` which is character length.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.1da9db641f353613a38fdabbab9d909e%40djangoproject.com.

[Django] #31838: django.contrib.gis.geos.error.GEOSException: Could not parse version info string "3.8.0-CAPI-1.13.1 "

[Django]

#31838: django.contrib.gis.geos.error.GEOSException: Could not parse version 
info
string "3.8.0-CAPI-1.13.1 "
-+
   Reporter:  palewire   |  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  Uncategorized  |Version:
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 Same deal as #20036, #17212, #20036 and I'm sure others. Using Python 2.7,
 Django 1.11.29 and the latest postgis installed by default on Ubuntu 20.04
 (a LTS release)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.f05928cca9a7fe46645de29d0f0ebca2%40djangoproject.com.

Re: [Django] #31829: Chaining KeyTransform with 'contains' lookup uses builtin lookup instead of overridden lookup

[Django]

#31829: Chaining KeyTransform with 'contains' lookup uses builtin lookup 
instead of
overridden lookup
-+-
 Reporter:  sage |Owner:  sage
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"2d8dcba03aae200aaa103ec1e69f0a0038ec2f85" 2d8dcba0]:
 {{{
 #!CommitTicketReference repository=""
 revision="2d8dcba03aae200aaa103ec1e69f0a0038ec2f85"
 Fixed #31829 -- Used JSONField __contains lookup on key transforms.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.74b1fd4618a1d48d1d0bc93fbd8a04df%40djangoproject.com.

Re: [Django] #31837: Possible manager migration bug

[Django]

#31837: Possible manager migration bug
+--
 Reporter:  Gordon Wrigley  |Owner:  nobody
 Type:  Uncategorized   |   Status:  new
Component:  Uncategorized   |  Version:  3.0
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Gordon Wrigley):

 Behaviour is the same on 3.1rc1

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.c79177f7acc0c414b53b26bf5240a1a5%40djangoproject.com.

Re: [Django] #24686: Support for Moving a model between two Django apps

[Django]

#24686: Support for Moving a model between two Django apps
---+-
 Reporter:  Alex Rothberg  |Owner:  Abhishek Bera
 Type:  New feature|   Status:  assigned
Component:  Migrations |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Abhishek Bera):

 Hi, I am new to django development so I started with this documentation
 ticket. I am struggling with the level of detail I should mention in the
 document. So far I just updated the param and mentioned what it does. Here
 is the diff :

 ddiff --git a/docs/ref/migration-operations.txt b/docs/ref/migration-
 operations.txt
 index d1620cce8e..f4a444e8e9 100644
 --- a/docs/ref/migration-operations.txt
 +++ b/docs/ref/migration-operations.txt
  ``RenameField``
  ---

 -.. class:: RenameField(model_name, old_name, new_name)
 +.. class:: RenameField(model_name, old_name, new_name,
 new_app_label=None)

  Changes a field's name (and, unless
 :attr:`~django.db.models.Field.db_column`
 -is set, its column name).
 +is set, its column name) or moves the Model to `new_app_label`.

 Also, what should be the branch name for this PR?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.2e3cd1dd2d87b96f1dfcfaa49c530ce1%40djangoproject.com.

Re: [Django] #24686: Support for Moving a model between two Django apps

[Django]

#24686: Support for Moving a model between two Django apps
---+-
 Reporter:  Alex Rothberg  |Owner:  Abhishek Bera
 Type:  New feature|   Status:  assigned
Component:  Migrations |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by Abhishek Bera):

 * owner:  nobody => Abhishek Bera
 * status:  new => assigned


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.056a68883b533af0c6cb8c9f57d5bd1a%40djangoproject.com.

Re: [Django] #31122: Clarify how the Lookup class follow the Query Expression API.

[Django]

#31122: Clarify how the Lookup class follow the Query Expression API.
--+
 Reporter:  Hongtao Ma|Owner:  AP Jama
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  3.0
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by AP Jama):

 * owner:  nobody => AP Jama
 * status:  new => assigned


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.d2c0ec5f196773594d4680321748b780%40djangoproject.com.

Re: [Django] #26624: Error when running sqlmigrate after dropping index (of index_together) without actually migrating

[Django]

#26624: Error when running sqlmigrate after dropping index (of index_together)
without actually migrating
-+-
 Reporter:  Akshesh Doshi|Owner:  
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  sqlmigrate db-   | Triage Stage:  Accepted
  indexes|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 It was also reported in #31834 that issue is reproducible on SQLite.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.ac9051bea639f0078f7ba5800bff61fd%40djangoproject.com.

Re: [Django] #31834: Cannot sqlmigrate on Django migrations that change unique_together

[Django]

#31834: Cannot sqlmigrate on Django migrations that change unique_together
+--
 Reporter:  Brіаn Lаі   |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  3.0
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  sqlmigrate  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Brіаn Lаі):

 I guess so. However you choose to triage and/or fix the item, I hope I am
 providing additional context by saying this bug can be reproduced with
 SQLite, whereas #26624 claims they could not.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.164cb02c8617154960f32fafc446a5a4%40djangoproject.com.

Re: [Django] #31783: Filtering on a field named `negate` raises a TypeError

[Django]

#31783: Filtering on a field named `negate` raises a TypeError
-+-
 Reporter:  Aaron Kirkbride  |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Simon Charette):

 * stage:  Accepted => Ready for checkin


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.c47cff991ad9045a2944f320389a2472%40djangoproject.com.

Re: [Django] #31837: Possible manager migration bug

[Django]

#31837: Possible manager migration bug
+--
 Reporter:  Gordon Wrigley  |Owner:  nobody
 Type:  Uncategorized   |   Status:  new
Component:  Uncategorized   |  Version:  3.0
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Description changed by Gordon Wrigley:

Old description:

> If I understand managers and migrations correctly then the change in this
> commit https://github.com/tolomea/django-
> tutorial/commit/e5df712ef10be91cd2e5d28c9df48e33254a2b10 produces a bad
> migration.
>
> Specifically I expect the migration to include both managers but it omits
> the "objects" manager.
>
> This causes a problem in the followup data migration
> https://github.com/tolomea/django-
> tutorial/commit/90825038c55913d74a23b1c5c2ba35268d0a1367 where
> Question.objects isn't available leading to {{{AttributeError: type
> object 'Question' has no attribute 'objects'}}}
>
> I have observed this in 3.0.8 and 2.2.14 (where I first ran into it)

New description:

 If I understand managers and migrations correctly then the change in this
 commit https://github.com/tolomea/django-
 tutorial/commit/e5df712ef10be91cd2e5d28c9df48e33254a2b10 produces a bad
 migration.

 Specifically I expect the migration to include both managers but it omits
 the "objects" manager.

 This causes a problem in the followup data migration
 https://github.com/tolomea/django-
 tutorial/commit/90825038c55913d74a23b1c5c2ba35268d0a1367 where
 Question.objects isn't available leading to {{{AttributeError: type object
 'Question' has no attribute 'objects'}}}

 I have observed this in 3.0.8 and 2.2.14 (where I first ran into it)

 Also I observed (on 2.2.14 didn't check this on 3.0.8) that adding objects
 to the concrete model (or an additional abstract model in between) fixes
 the problem.

--

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.70ecd9524d180cb0400c35c6e27c6382%40djangoproject.com.

Re: [Django] #31783: Filtering on a field named `negate` raises a TypeError

[Django]

#31783: Filtering on a field named `negate` raises a TypeError
-+-
 Reporter:  Aaron Kirkbride  |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Aaron Kirkbride):

 Replying to [comment:5 Hasan Ramezani]:

 Thanks Hasan for creating the PR :) Sorry I didn't get round to this
 earlier.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.e25876731e1931bd67b7d9ab1c8fcc69%40djangoproject.com.

[Django] #31837: Possible manager migration bug

[Django]

#31837: Possible manager migration bug
--+
   Reporter:  Gordon Wrigley  |  Owner:  nobody
   Type:  Uncategorized   | Status:  new
  Component:  Uncategorized   |Version:  3.0
   Severity:  Normal  |   Keywords:
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 If I understand managers and migrations correctly then the change in this
 commit https://github.com/tolomea/django-
 tutorial/commit/e5df712ef10be91cd2e5d28c9df48e33254a2b10 produces a bad
 migration.

 Specifically I expect the migration to include both managers but it omits
 the "objects" manager.

 This causes a problem in the followup data migration
 https://github.com/tolomea/django-
 tutorial/commit/90825038c55913d74a23b1c5c2ba35268d0a1367 where
 Question.objects isn't available leading to {{{AttributeError: type object
 'Question' has no attribute 'objects'}}}

 I have observed this in 3.0.8 and 2.2.14 (where I first ran into it)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.94c93257df2b584e34db0b8e881b3d30%40djangoproject.com.

Re: [Django] #31783: Filtering on a field named `negate` raises a TypeError

[Django]

#31783: Filtering on a field named `negate` raises a TypeError
-+-
 Reporter:  Aaron Kirkbride  |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Hasan Ramezani):

 * owner:  Aaron Kirkbride => Hasan Ramezani
 * has_patch:  0 => 1


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.58384bc9a685326383d0cd671a429b15%40djangoproject.com.

Re: [Django] #29324: Change Settings to raise ImproperlyConfigured on SECRET_KEY; not initialization

[Django]

#29324: Change Settings to raise ImproperlyConfigured on SECRET_KEY; not
initialization
-+-
 Reporter:  Jon Dufresne |Owner:  Florian
 Type:   |  Apolloner
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Accepted => Ready for checkin


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.2d9d0cce7dc922d387ac66621dd45ff7%40djangoproject.com.

Re: [Django] #31792: Use `EXISTS(SELECT 1 ...)` for subqueries

[Django]

#31792: Use `EXISTS(SELECT 1 ...)` for subqueries
-+-
 Reporter:  w0rp |Owner:  Harpreet
 Type:   |  Sharma
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  3.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Harpreet Sharma):

 * owner:  (none) => Harpreet Sharma
 * status:  new => assigned


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.be22e92f95d04519583c6991251ed18e%40djangoproject.com.

Re: [Django] #25139: ModelFormSet: allow swapping unique values

[Django]

#25139: ModelFormSet: allow swapping unique values
--+-
 Reporter:  Jon Dufresne  |Owner:  Parth Patil
 Type:  New feature   |   Status:  assigned
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-
Changes (by Sergey Fedoseev):

 * cc: Sergey Fedoseev (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.fed2ec7b890370c2864fc9e197576535%40djangoproject.com.

Re: [Django] #31829: Chaining KeyTransform with 'contains' lookup uses builtin lookup instead of overridden lookup

[Django]

#31829: Chaining KeyTransform with 'contains' lookup uses builtin lookup 
instead of
overridden lookup
-+-
 Reporter:  sage |Owner:  sage
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.5d1b1d22607bce9f0de484c87604ff1a%40djangoproject.com.

Re: [Django] #31836: JSONField's __contains and __contained_by lookups don't work with nested values on SQLite.

[Django]

#31836: JSONField's __contains and __contained_by lookups don't work with nested
values on SQLite.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"247bcef6b4f8625e80b6f07e264b7bbdf330194d" 247bcef6]:
 {{{
 #!CommitTicketReference repository=""
 revision="247bcef6b4f8625e80b6f07e264b7bbdf330194d"
 [3.1.x] Fixed #31836 -- Dropped support for JSONField __contains and
 __contained_by lookups on SQLite.

 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".

 Backport of ba691933cee375195c9c50f333dd4b2a3abbb726 from master.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.624371f3191fc05cdd25835d99352c4e%40djangoproject.com.

Re: [Django] #31836: JSONField's __contains and __contained_by lookups don't work with nested values on SQLite.

[Django]

#31836: JSONField's __contains and __contained_by lookups don't work with nested
values on SQLite.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"ba691933cee375195c9c50f333dd4b2a3abbb726" ba69193]:
 {{{
 #!CommitTicketReference repository=""
 revision="ba691933cee375195c9c50f333dd4b2a3abbb726"
 Fixed #31836 -- Dropped support for JSONField __contains and
 __contained_by lookups on SQLite.

 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".
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.bb1ccf0cc172622b32242d9fd973a396%40djangoproject.com.

Re: [Django] #31836: JSONField's __contains and __contained_by lookups don't work with nested values on SQLite.

[Django]

#31836: JSONField's __contains and __contained_by lookups don't work with nested
values on SQLite.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Accepted => Ready for checkin


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.fe393124dafa8af060252407a518bae2%40djangoproject.com.

Re: [Django] #30165: Deprecate ugettext(), ugettext_lazy(), ugettext_noop(), ungettext(), and ungettext_lazy()

[Django]

#30165: Deprecate ugettext(), ugettext_lazy(), ugettext_noop(), ungettext(), and
ungettext_lazy()
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"bac5777bff8e8d8189193438b5af52f158a3f2a4" bac5777]:
 {{{
 #!CommitTicketReference repository=""
 revision="bac5777bff8e8d8189193438b5af52f158a3f2a4"
 Refs #30165 -- Removed leftover 'u' prefix.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.5423e57b7571e1a1759ac29b3dfa4675%40djangoproject.com.

Re: [Django] #31836: JSONField's __contains and __contained_by lookups don't work with nested values on SQLite.

[Django]

#31836: JSONField's __contains and __contained_by lookups don't work with nested
values on SQLite.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/13250 PR]

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.4d3dcde9c9a0e45da189ad8aa392e307%40djangoproject.com.

Re: [Django] #31836: JSONField's __contains and __contained_by lookups don't work with nested values on SQLite.

[Django]

#31836: JSONField's __contains and __contained_by lookups don't work with nested
values on SQLite.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * owner:  nobody => felixxm
 * status:  new => assigned


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.c9e5268c4abde026518901b567136382%40djangoproject.com.

Re: [Django] #31821: FILE_UPLOAD_PERMISSIONS docs contain outdated note.

[Django]

#31821: FILE_UPLOAD_PERMISSIONS docs contain outdated note.
-+-
 Reporter:  Pavel Mises  |Owner:  Harpreet
 Type:   |  Sharma
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
  FILE_UPLOAD_PERMISSIONS|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"31164445599d8c1e69147485e418c6acc67e1278" 3116444]:
 {{{
 #!CommitTicketReference repository=""
 revision="31164445599d8c1e69147485e418c6acc67e1278"
 [3.1.x] Fixed #31821 -- Removed outdated note in FILE_UPLOAD_PERMISSIONS
 docs.

 Follow up to 22aab8662f0368b63f91f2526bdd0532524bc0fe

 Backport of 248d03fbe932b0844c628e56dafba334f9e028e4 from master
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.0c5d269d2b5d0011cbec49f9f6acdedc%40djangoproject.com.

Re: [Django] #31835: JSONField's __contains lookup doesn't work in nested values on Oracle.

[Django]

#31835: JSONField's __contains lookup doesn't work in nested values on Oracle.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"028a5f86f22d4be0746cbd38d09d6961024b2ef7" 028a5f8]:
 {{{
 #!CommitTicketReference repository=""
 revision="028a5f86f22d4be0746cbd38d09d6961024b2ef7"
 [3.1.x] 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".
 Backport of 02447fb133b53ec7d0ff068cc08f06fdf8817ef7 from master
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.79f42eb181b27af3b09a359c9535e65d%40djangoproject.com.

Re: [Django] #31835: JSONField's __contains lookup doesn't work in nested values on Oracle.

[Django]

#31835: JSONField's __contains lookup doesn't work in nested values on Oracle.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"02447fb133b53ec7d0ff068cc08f06fdf8817ef7" 02447fb1]:
 {{{
 #!CommitTicketReference repository=""
 revision="02447fb133b53ec7d0ff068cc08f06fdf8817ef7"
 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".
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.115fdc8f3066f7835c21873687033387%40djangoproject.com.

Re: [Django] #31836: JSONField's __contains and __contained_by lookups don't work with nested values on SQLite.

[Django]

#31836: JSONField's __contains and __contained_by lookups don't work with nested
values on SQLite.
-+-
 Reporter:  felixxm  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by felixxm):

 I've attached a draft solution but it's really hot and it doesn't handle
 list with dicts (...deep rabbit hole). IMO we should drop support for
 these lookups on SQLite, at least for now. Testing containment of
 `JSONField` is really complicated, I hope SQLite and Oracle will prepare
 native solutions in future versions.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.17938a3dcd744af1e0875126bcce433d%40djangoproject.com.

Re: [Django] #31836: JSONField's __contains and __contained_by lookups don't work with nested values on SQLite.

[Django]

#31836: JSONField's __contains and __contained_by lookups don't work with nested
values on SQLite.
-+-
 Reporter:  felixxm  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * Attachment "draft.py" added.

 Draft.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.c582701854b3bd4e9d27c17a507770b9%40djangoproject.com.

Re: [Django] #31827: Add test runner option to show N slowest tests

[Django]

#31827: Add test runner option to show N slowest tests
-+-
 Reporter:  Ahmad A. Hussein |Owner:  Ahmad A.
 |  Hussein
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * easy:  1 => 0
 * stage:  Unreviewed => Accepted


Comment:

 A lot of folks use `django-admin test` so I'm minded to accept this for a
 follow-up to #31811.

 [https://github.com/django/django/pull/13224/#issuecomment-664913219 Some
 comments on the PR there]: `--timing` with an elevated verbosity might be
 a good way to say, "show top N slowest tests".

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.bc16aab626379c5f898b0f63f5cce783%40djangoproject.com.

Re: [Django] #31836: JSONField's __contains and __contained_by lookups don't work with nested values on SQLite.

[Django]

#31836: JSONField's __contains and __contained_by lookups don't work with nested
values on SQLite.
-+-
 Reporter:  felixxm  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Unreviewed => Accepted


Comment:

 OK, g... — Just a case of doc-ing  the limitations. 🤨
 (Thanks)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.2331ce47071fde9e121196dd180d0ca2%40djangoproject.com.

[Django] #31836: JSONField's __contains and __contained_by lookups don't work with nested values on SQLite.

[Django]

#31836: JSONField's __contains and __contained_by lookups don't work with nested
values on SQLite.
-+-
   Reporter:  felixxm|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  3.1
  layer (models, ORM)|
   Severity:  Release|   Keywords:
  blocker|
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 SQLite doesn't provide a native way for testing containment of
 `JSONField`. 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"''.

 I'm not sure if it's feasible to emulate it in Python.

 Some (not really complicated) examples that don't work:
 {{{
 diff --git a/tests/model_fields/test_jsonfield.py
 b/tests/model_fields/test_jsonfield.py
 index 9a9e1a1286..1acc5af73e 100644
 --- a/tests/model_fields/test_jsonfield.py
 +++ b/tests/model_fields/test_jsonfield.py
 @@ -449,9 +449,14 @@ class TestQuerying(TestCase):
  tests = [
  ({}, self.objs[2:5] + self.objs[6:8]),
  ({'baz': {'a': 'b', 'c': 'd'}}, [self.objs[7]]),
 +({'baz': {'a': 'b'}}, [self.objs[7]]),
 +({'baz': {'c': 'd'}}, [self.objs[7]]),
  ({'k': True, 'l': False}, [self.objs[6]]),
  ({'d': ['e', {'f': 'g'}]}, [self.objs[4]]),
 +({'d': ['e']}, [self.objs[4]]),
  ([1, [2]], [self.objs[5]]),
 +([1], [self.objs[5]]),
 +([[2]], [self.objs[5]]),
  ({'n': [None]}, [self.objs[4]]),
  ({'j': None}, [self.objs[4]]),
  ]
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.9f9556beab27c415ccee5b1e4c22954d%40djangoproject.com.

Re: [Django] #31811: Add optional timing outputs to the test runner

[Django]

#31811: Add optional timing outputs to the test runner
-+-
 Reporter:  Ahmad A. Hussein |Owner:  Ahmad A.
 |  Hussein
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  timing, test runner  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * needs_better_patch:  0 => 1


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.ba0e54fbdaee9814f90f8629ed4a085b%40djangoproject.com.

Re: [Django] #31835: JSONField's __contains lookup doesn't work in nested values on Oracle.

[Django]

#31835: JSONField's __contains lookup doesn't work in nested values on Oracle.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/13248 PR]

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.216577754b7a3e761cb02e1b74160c4f%40djangoproject.com.

Re: [Django] #27996: Add pgcrypto extension and GEN_RANDOM_UUID function to contrib.postgres

[Django]

#27996: Add pgcrypto extension  and GEN_RANDOM_UUID function to contrib.postgres
-+-
 Reporter:  Paolo Melchiorre |Owner:  Paolo
 |  Melchiorre
 Type:  New feature  |   Status:  closed
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  uuid extension   | Triage Stage:  Ready for
  function random postgresql |  checkin
  cryptography   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"628c4a26eee93417bb7161aa393dffb3f4c146b2" 628c4a2]:
 {{{
 #!CommitTicketReference repository=""
 revision="628c4a26eee93417bb7161aa393dffb3f4c146b2"
 Refs #27996 -- Doc'd no extension required for RandomUUID() on PostgreSQL
 13+.

 https://www.postgresql.org/docs/13/functions-uuid.html
 https://www.postgresql.org/docs/13/pgcrypto.html#id-1.11.7.34.10.5
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.95fa7171a140ff92e0ac37b8b12b9adb%40djangoproject.com.

Re: [Django] #27395: Allow generating '

[Django]

#27395: Allow generating ' 0


Comment:

 Pushed more recommended changes after review by David Smith; please
 consider merge again :)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.435c0860f3e076e0c9c8a438eee5cdb3%40djangoproject.com.

Re: [Django] #31835: JSONField's __contains lookup doesn't work in nested values on Oracle. (was: JSONField's __cointains lookup doesn't work in nested values on Oracle.)

[Django]

#31835: JSONField's __contains lookup doesn't work in nested values on Oracle.
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.64487df24d4b195c074febc088e57d73%40djangoproject.com.

[Django] #31835: JSONField's __cointains lookup doesn't work in nested values on Oracle.

[Django]

#31835: JSONField's __cointains lookup doesn't work in nested values on Oracle.
-+-
   Reporter:  felixxm|  Owner:  felixxm
   Type:  Bug| Status:  assigned
  Component:  Database   |Version:  3.1
  layer (models, ORM)|
   Severity:  Release|   Keywords:
  blocker|
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Oracle doesn't provide a native way for testing containment of JSONField.
 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"''.

 It looks that building multi-level/recursive filters with `JSON_EXISTS()`
 is the only feasible way, but it's really complicated and can be clunky.

 I think we should drop this lookup on Oracle and raise
 `NotSupportedError`.

 Some examples:
 {{{
 diff --git a/tests/model_fields/test_jsonfield.py
 b/tests/model_fields/test_jsonfield.py
 index 3ce7fc51a9..b659675ec8 100644
 --- a/tests/model_fields/test_jsonfield.py
 +++ b/tests/model_fields/test_jsonfield.py
 @@ -445,8 +445,12 @@ class TestQuerying(TestCase):
  tests = [
  ({}, self.objs[2:5] + self.objs[6:8]),
  ({'baz': {'a': 'b', 'c': 'd'}}, [self.objs[7]]),
 +({'baz': {'a': 'b'}}, [self.objs[7]]),
 +({'baz': {'c': 'd'}}, [self.objs[7]]),
  ({'k': True, 'l': False}, [self.objs[6]]),
  ({'d': ['e', {'f': 'g'}]}, [self.objs[4]]),
 +({'d': ['e']}, [self.objs[4]]),
 +({'d': [{'f': 'g'}]}, [self.objs[4]]),
  ([1, [2]], [self.objs[5]]),
  ({'n': [None]}, [self.objs[4]]),
  ({'j': None}, [self.objs[4]]),
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.ec50ecc3f10ac299388643b9934752a5%40djangoproject.com.