Re: [Django] #23718: TEST_MIRROR setting doesn't work as expected (and has no tests)

[Django]

#23718: TEST_MIRROR setting doesn't work as expected (and has no tests)
---+-
 Reporter:  Ilya Baryshev  |Owner:  Rag Sagar
 Type:  Bug|   Status:  assigned
Component:  Testing framework  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords:  replica testing| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Simon Charette):

 Rag Sagar, I'm afraid none of the above solution will work appropriately.

 Here's the problem:

 If you configure mirrors to create a new connection to mirrored connection
 settings then changes performed within a transaction using the mirrored
 connection won't be visible in the mirror connection per `READ COMMITED`
 transaction isolation definition. That's the case right now.

 Using `READ UNCOMMITTED` on the mirror connection seems to be a no-go from
 limited support and the fact MySQL seems inconsistent and reusing the same
 connection has confuses transaction management.

 The only solutions I see going forward are:

 1. Document this caveats of `TEST_MIRROR` and `TestCase` transaction
 wrapping interactions.
 2. Invest more time trying to get the `connections` repointing during
 `TestCase.setUpClass` working to get the suite passing and document the
 new caveats.

 In both cases we could at least do 1. or warn about it to make it clear
 this is not currently supported.

-- 
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.4c7a25df7cfb6bbce7fdca0f3d5b%40djangoproject.com.

Re: [Django] #28992: Querying GenericIPAddressField with a space crashes with DataError on PostgreSQL

[Django]

#28992: Querying GenericIPAddressField with a space crashes with DataError on
PostgreSQL
-+-
 Reporter:  Vlada Macek  |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 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 Simon Charette):

 I know some lookup raise `ValueError` or `TypeError` when an invalid value
 is provided but none raise `ValidationError` AFAIK. IMO this is an issue
 similar to #29915 where a specialized `__contains` lookup must be
 implemented for `GenericIPAddressField`.

-- 
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.ad27873d3e82a3fe55a44263dc2a2cd8%40djangoproject.com.

Re: [Django] #28992: Querying GenericIPAddressField with a space crashes with DataError on PostgreSQL

[Django]

#28992: Querying GenericIPAddressField with a space crashes with DataError on
PostgreSQL
-+-
 Reporter:  Vlada Macek  |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   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 Can Sarıgöl):

 * owner:  nobody => Can Sarıgöl
 * status:  new => assigned
 * has_patch:  0 => 1
 * version:  1.11 => master


Comment:

 [https://github.com/django/django/pull/11682 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/064.2f7554610872a40f2c67f09eb30656f1%40djangoproject.com.

Re: [Django] #23718: TEST_MIRROR setting doesn't work as expected (and has no tests)

[Django]

#23718: TEST_MIRROR setting doesn't work as expected (and has no tests)
---+-
 Reporter:  Ilya Baryshev  |Owner:  Rag Sagar
 Type:  Bug|   Status:  assigned
Component:  Testing framework  |  Version:  1.7
 Severity:  Normal |   Resolution:
 Keywords:  replica testing| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+-

Comment (by Rag Sagar):

 @Simon Charette Since `READ_UNCOMMITED` is not supported in postgres,
 Should I explore further in that direction? The solution that comes up on
 my mind is pointing mirror connections to mirrored for the duration of the
 `TestCase`. But that has the issues you pointed out. So I am bit confused
 which way I should go.

-- 
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.b2ec859bb7710b6999e3de115e94fa20%40djangoproject.com.

Re: [Django] #29260: Remove UPDATE query when saving a new model instance with a primary key that has a default

[Django]

#29260: Remove UPDATE query when saving a new model instance with a primary key
that has a default
-+-
 Reporter:  user0007 |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  2.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:  0|UI/UX:  0
-+-
Changes (by Hasan Ramezani):

 * owner:  HyunTae Hwang => Hasan Ramezani
 * has_patch:  0 => 1


Comment:

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

-- 
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.6d65076e25cab4892a9e721c22dda954%40djangoproject.com.

Re: [Django] #28752: Prevent django.setup() from running multiple times

[Django]

#28752: Prevent django.setup() from running multiple times
-+-
 Reporter:  pascal chambon   |Owner:  pascal
 Type:   |  chambon
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  1.11
 Severity:  Normal   |   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 pascal chambon):

 * needs_better_patch:  1 => 0
 * 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/063.dec6a8bfd62febdc0e0e2333f55b158f%40djangoproject.com.

Re: [Django] #29955: Support dwithin lookup on F expressions for distance stored in model

[Django]

#29955: Support dwithin lookup on F expressions for distance stored in model
-+-
 Reporter:  Peter Bex|Owner:  Simon
 |  Charette
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  distance, query  | Triage Stage:  Accepted
  builder, F expressions |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * owner:  nobody => Simon Charette
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 Thanks for the test case Mariusz, here's the patch.

 https://github.com/django/django/pull/11681

 This was missed when adding support for distance expression #25499 most
 probably because of the `sql_template` override.

-- 
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.d7dc6fbd41dfd9b39c7d25e8a87b2c8a%40djangoproject.com.

Re: [Django] #30712: Add support for defaults on BLOB and TEXT columns on MySQL 8.0.13+

[Django]

#30712: Add support for defaults on BLOB and TEXT columns on MySQL 8.0.13+
-+-
 Reporter:  Adam (Chainz)|Owner:  Nasir
  Johnson|  Hussain
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  MySQL, default   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * 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/068.c362aab1aab807fa1bb7471554a7ea4c%40djangoproject.com.

Re: [Django] #30712: Add support for defaults on BLOB and TEXT columns on MySQL 8.0.13+

[Django]

#30712: Add support for defaults on BLOB and TEXT columns on MySQL 8.0.13+
-+-
 Reporter:  Adam (Chainz)|Owner:  Nasir
  Johnson|  Hussain
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  MySQL, default   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nasir Hussain):

 * 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/068.c277e43f71acf2129df67472509b390b%40djangoproject.com.

Re: [Django] #30712: Add support for defaults on BLOB and TEXT columns on MySQL 8.0.13+

[Django]

#30712: Add support for defaults on BLOB and TEXT columns on MySQL 8.0.13+
-+-
 Reporter:  Adam (Chainz)|Owner:  Nasir
  Johnson|  Hussain
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  MySQL, default   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Nasir Hussain):

 Created a PR [https://github.com/django/django/pull/11679
 django/django/pull/11679]

-- 
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/068.1ee54990a344bab90c398319b174bac1%40djangoproject.com.

Re: [Django] #29545: Nested OuterRef not looking on the right model for the field.

[Django]

#29545: Nested OuterRef not looking on the right model for the field.
-+-
 Reporter:  Aaron Lisman |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  outerref, subquery   | Triage Stage:  Accepted
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:"8b4a43dda702fe72c254388f1be2c0c75b7a3efc" 8b4a43d]:
 {{{
 #!CommitTicketReference repository=""
 revision="8b4a43dda702fe72c254388f1be2c0c75b7a3efc"
 Fixed #29545 -- Fixed using filter lookups againts nested subquery
 expressions.

 Made sql.Where resolve lhs of its child nodes. This is necessary to
 allow filter lookups against nested subquery expressions to properly
 resolve their OuterRefs to Cols.

 Thanks Oskar Persson for the simplified test case.
 }}}

-- 
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.3ac99f52ffed711559cdbc44e940a513%40djangoproject.com.

Re: [Django] #30712: Add support for defaults on BLOB and TEXT columns on MySQL 8.0.13+

[Django]

#30712: Add support for defaults on BLOB and TEXT columns on MySQL 8.0.13+
-+-
 Reporter:  Adam (Chainz)|Owner:  Nasir
  Johnson|  Hussain
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  MySQL, default   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Nasir Hussain):

 * status:  new => assigned
 * owner:  nobody => Nasir Hussain


-- 
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/068.b7c40672ec642b573f6e1305fa4a7c94%40djangoproject.com.

Re: [Django] #29545: Nested OuterRef not looking on the right model for the field.

[Django]

#29545: Nested OuterRef not looking on the right model for the field.
-+-
 Reporter:  Aaron Lisman |Owner:  Simon
 |  Charette
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  outerref, subquery   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Can Sarıgöl):

 Sorry I misinterpreted. Simon is right. Thanks for the explanation.

-- 
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.8a516ddc482abe722ebbba3cf0f717ff%40djangoproject.com.

Re: [Django] #30691: Change uuid field to FK does not create dependency

[Django]

#30691: Change uuid field to FK does not create dependency
+
 Reporter:  Dart|Owner:  Dart
 Type:  Bug |   Status:  assigned
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:
 Keywords:  UUID, FK| Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by Dmitrij Strelnikov):

 I'm pretty sure your db change interfere with migration best practice.
 You are changing field type, which have to be done in two steps.
 And your migrations are not telling django what should be done with data
 in uuid field contains when migrate.

-- 
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.d4d2679a2940f42527d9900143958593%40djangoproject.com.

[Django] #30713: ListView queryset issue

[Django]

#30713: ListView queryset issue
-+-
   Reporter:  Dmitrij|  Owner:  nobody
  Strelnikov |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.2
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  queryset
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Hi guys,
 is this intentional behaviour or not?


 {{{
 class SomeQuerySet(models.QuerySet):
 def active(self):
 print('active')
 data = cache.get(CACHE_KEY)
 if data is None:
 print('no cache')
 data =
 
self.select_related('related').filter(date_expired__gte=timezone.localtime().now()).filter(
 some__is_active=True).order_by('-date_activated')
 cache.set(CACHE_KEY, data, 30)
 return data

 }}}


 {{{
 class QSSomeListView(ListView):
 queryset = Some.objects.active()
 }}}

 {{{
 class GetQSSomeListView(ListView):
 def get_queryset(self):
 return Some.objects.active()
 }}}

 QSSomeListView never print anything from `active()` method on page access,
 and actually never hit cache. It print only `active` once at project
 startup.

 GetQSSomeListView works as expected.

 If its intentional, could you please explain / point me why so?
 Thank you.

-- 
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/053.8f38a77d6091772e093d82595ec6ddda%40djangoproject.com.

Re: [Django] #30694: Document FileResponse does not seek its file source

[Django]

#30694: Document FileResponse does not seek its file source
---+
 Reporter:  Claude Paroz   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  2.2
 Severity:  Normal |   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 Carlton Gibson ):

 In [changeset:"556cef1ba8facbd3231f6351956a6581c6367632" 556cef1]:
 {{{
 #!CommitTicketReference repository=""
 revision="556cef1ba8facbd3231f6351956a6581c6367632"
 [2.2.x] Fixed #30694 -- Documented FileResponse does not seek its file
 source.

 Backport of 7203efb799969b4662ecb58f4cefd2a5f2e0062b 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.2185df00c33d695d869caaa3d5f013cf%40djangoproject.com.

Re: [Django] #30694: Document FileResponse does not seek its file source

[Django]

#30694: Document FileResponse does not seek its file source
---+
 Reporter:  Claude Paroz   |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  2.2
 Severity:  Normal |   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 Carlton Gibson ):

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


Comment:

 In [changeset:"7203efb799969b4662ecb58f4cefd2a5f2e0062b" 7203efb7]:
 {{{
 #!CommitTicketReference repository=""
 revision="7203efb799969b4662ecb58f4cefd2a5f2e0062b"
 Fixed #30694 -- Documented FileResponse does not seek its file source.
 }}}

-- 
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.43db95cb508c0af7e19e873aa8f1%40djangoproject.com.

Re: [Django] #29955: Support dwithin lookup on F expressions for distance stored in model

[Django]

#29955: Support dwithin lookup on F expressions for distance stored in model
-+-
 Reporter:  Peter Bex|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  distance, query  | Triage Stage:  Accepted
  builder, F expressions |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by felixxm):

 Simon it still doesn't work. I attached test case that raises
 {{{
 File "django/django/db/backends/utils.py", line 86, in _execute
 return self.cursor.execute(sql, params)
 IndexError: tuple index out of range
 }}}

-- 
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.a6c4de52a0657abf6cddd23fa9d63d13%40djangoproject.com.

Re: [Django] #29955: Support dwithin lookup on F expressions for distance stored in model

[Django]

#29955: Support dwithin lookup on F expressions for distance stored in model
-+-
 Reporter:  Peter Bex|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  GIS  |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  distance, query  | Triage Stage:  Accepted
  builder, F expressions |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * Attachment "test-29955.diff" 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/065.bf6c2d47fe8a3d6649826196d789c31c%40djangoproject.com.