Re: [Django] #34533: OuterRef not resolved as part oh ORDER BY clause

[Django]

#34533: OuterRef not resolved as part oh ORDER BY clause
-+-
 Reporter:  REGNIER Guillaume|Owner:  REGNIER
 |  Guillaume
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  OuterRef, OrderBy| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jordan Bae):

 * owner:  (none) => REGNIER Guillaume
 * 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/010701885b1ae1e1-8e785dae-b12a-47bc-a724-9ac1ea6d62fb-00%40eu-central-1.amazonses.com.

Re: [Django] #34533: OuterRef not resolved as part oh ORDER BY clause

[Django]

#34533: OuterRef not resolved as part oh ORDER BY clause
-+-
 Reporter:  REGNIER Guillaume|Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  OuterRef, OrderBy| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jordan Bae):

 * owner:  Jordan Bae => (none)
 * status:  assigned => new


Comment:

 no worry! i think it's better tyou bring this ticket. i deassign this
 ticket.

-- 
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/010701885b1a3cbf-2f10a3b8-66c7-46c7-9913-d98cf87449ec-00%40eu-central-1.amazonses.com.

Re: [Django] #34564: returning None instead of zero in Count annotation

[Django]

#34564: returning None instead of zero in Count annotation
-+-
 Reporter:  Amin Aminian |Owner:  Amin
 |  Aminian
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  count, orm,  | Triage Stage:  Accepted
  annotate   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 Django doesn't support TimescaleDB so any change against it is not
 considered a regression from our perspective. You might have run into bugs
 with TimescaleDB for all we know.

 The fact you cannot reproduce against SQLite, Postgres, MySQL, or Oracle
 might explain why this was not caught by the test suite in the first place
 which would make more sense given how common such annotations are.

 Here are my attempts at reproducing

 - [https://dbfiddle.uk/eUmjoLFI Postgres]
 - [https://dbfiddle.uk/XXhzrttD MySQL]
 - [https://dbfiddle.uk/esgjJ2cA 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/010701885af2de66-b9e0f01c-8b77-4436-a26a-081cce96e2e4-00%40eu-central-1.amazonses.com.

Re: [Django] #34534: Reduce index/constraints operations.

[Django]

#34534: Reduce index/constraints operations.
--+
 Reporter:  David Sanders |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  dev
 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
--+

Comment (by Adam Johnson):

 Thank you for reporting this David, making the PR Akash, and reviewing
 Mariusz. 👏

 I was just looking at a migration with consecutive add + remove operations
 for the same constraints, wondering why they weren't optimized. Glad to
 see they will be in the future.

-- 
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/0107018859ecf54c-1309e530-5ee6-4e52-a1a3-601a6acf339f-00%40eu-central-1.amazonses.com.

Re: [Django] #34564: returning None instead of zero in Count annotation

[Django]

#34564: returning None instead of zero in Count annotation
-+-
 Reporter:  Amin Aminian |Owner:  Amin
 |  Aminian
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  count, orm,  | Triage Stage:  Accepted
  annotate   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Amin Aminian):

 Hi again.
 I was trying to write a regression test that I faced an issue.
 Apparently, `Count` function is returning 0 usually. But I was unlucky
 enough to face some situations that `Count` return `None`.

 One situation is during my tests, when using `Timescaledb` (Postgres
 extension). In this scenario, I'm getting `None` instead of 0 when using
 `Count`.
 And the another situation is on production server, when some complicated
 queries are executed and I'm getting None there too. I cannot find out why
 that leads to `None`, as I get 0 when using similar queries.

 So I'm basically asking, do you know some simple scenarios that DB would
 return None ? (I suppose the old `convert_value` function was there for
 those scenarios)

 And if your not, is it valid to use `Timescaledb` in test ? (Actually I
 have written such a test already for TDD development during 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/0107018859cd7caa-687b54be-bafb-430e-846e-79b345a704fe-00%40eu-central-1.amazonses.com.

Re: [Django] #21080: collectstatic post-processing fails for references inside comments

[Django]

#21080: collectstatic post-processing fails for references inside comments
-+
 Reporter:  shreyas@…|Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by Manel Clos):

 * cc: Manel Clos (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/0107018858dbd25d-3089c2e5-745d-47c2-8ed0-29aaae0a7b81-00%40eu-central-1.amazonses.com.

Re: [Django] #30355: Specifying custom manager doesn't work with prefetch

[Django]

#30355: Specifying custom manager doesn't work with prefetch
---+---
 Reporter:  Kyle Mulka |Owner:  Akash Kumar Sen
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  dev
 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 Akash Kumar Sen):

 * cc: Akash Kumar Sen (added)
 * owner:  (none) => Akash Kumar Sen
 * has_patch:  0 => 1
 * status:  new => assigned


Comment:

 For me it also seems a documentation issue, as the same results can be
 achieved by obtaining other means. Created a documentation patch
 https://github.com/django/django/pull/16900

-- 
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/0107018858cb11ca-e4a3b746-3cf7-4949-a525-308968855812-00%40eu-central-1.amazonses.com.

Re: [Django] #34595: format_html() should explicitly mention that format_string is not escaped and that result is safe

[Django]

#34595: format_html() should explicitly mention that format_string is not 
escaped
and that result is safe
--+
 Reporter:  Natalia Bidart|Owner:  AP Jama
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Template system   |  Version:  4.2
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |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/010701885789f9ae-98e03cde-3d09-494a-95b2-284dc8e78eb0-00%40eu-central-1.amazonses.com.