Re: [Django] #30602: Raise ValueError in Extract lookups that don't work properly with DurationField.

[Django]

#30602: Raise ValueError in Extract lookups that don't work properly with
DurationField.
-+-
 Reporter:  cecedille1   |Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   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:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * type:  Bug => Cleanup/optimization
 * easy:  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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.0d550d107634f6ea11dcfe111f53bc12%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30633: Group by concat(field1, field2) producing wrong result. (was: Group by concat(field1, field2) producing wrong result)

[Django]

#30633: Group by concat(field1,field2) producing wrong result.
-+-
 Reporter:  bishwadeep   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  mysql group by   | 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
 * component:  Uncategorized => Database layer (models, ORM)
 * version:  2.2 => master
 * resolution:   => invalid


Comment:

 I'm not sure what exactly you want to achieve because your expected query
 and Django queryset are slightly different, but my understanding is that
 `values()` is missing:
 {{{
 query.annotate(person=Concat('field1',
 'field2')).values('person').annotate(Count('person', distinct=True))
 }}}

 Moreover this is a support question not a bug in Django, please use one of
 [https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels
 support channels].

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.dd33ce9c23b38fd3fb1020ece54dc3dd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #30633: Group by concat(field1, field2) producing wrong result

[Django]

#30633: Group by concat(field1,field2) producing wrong result
-+
   Reporter:  bishwadeep |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  2.2
   Severity:  Normal |   Keywords:  mysql group by
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 I am new to Django and I am enjoying it. I ran into an issue while
 creating a SQL query for my project. I want the following query to run
 using Django
 Query:
 Select id,field1,field2,field3 FROM table WHERE field1 = somevalue
 Group by concat(field1,field2) ORDER BY somefield

 However I am not able to get the desired query. It keeps on adding group
 by id which is not what I want.
 Django query:
 result = query.annotate(person=Concat(F('field1'),
 F('field2'))).annotate(Count('person', distinct=True))
 Outputs:
 SELECT id FROM table WHERE my condition GROUP BY id ORDER BY field

 Please let me know if you have any questions.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/053.c3a2cf804f382eeedaa75bc8f66bead1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30602: Raise ValueError in Extract lookups that don't work properly with DurationField.

[Django]

#30602: Raise ValueError in Extract lookups that don't work properly with
DurationField.
-+-
 Reporter:  cecedille1   |Owner:  Hasan
 |  Ramezani
 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 Hasan Ramezani):

 * owner:  cecedille1 => 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.b2fc9ddedf8896b6022377187b2c9eb9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30632: Pagination for FormSet

[Django]

#30632: Pagination for FormSet
-+---
 Reporter:  Parth Patil  |Owner:  Parth Patil
 Type:  New feature  |   Status:  closed
Component:  Forms|  Version:  2.2
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+---
Changes (by Carlton Gibson):

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


Comment:

 Hey Parth. I think we need to pin down the use-case before moving forward
 with this. Let's do that on the email.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.b18f6bcbda1a1d8174614a978affb5b5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30632: Pagination for FormSet

[Django]

#30632: Pagination for FormSet
-+---
 Reporter:  Parth Patil  |Owner:  Parth Patil
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  2.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+---

Comment (by Parth Patil):

 Replying to [comment:4 felixxm]:
 > because you will be able to work only on a single page i.e. only with a
 subset of forms from formset.

 I agree with that, but I meant this feature to be more as a method of
 representation of data rather than taking input from the user.

 Replying to [comment:5 Carlton Gibson]:
 > In this case don’t you paginate the queryset prior to creating the
 FormSet?

 I guess I'm thinking of a very specific example where the queryset is
 itself large enough, like a blog having over 100 replies.

 
 It's more like I see this being useful if used with models, this will give
 a quick way of representing different models using formsets, where even
 the queryset is large enough.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.5ea3d7c7e801cf34aab39e607f184d27%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30557: order_by() a parent model crash when Meta.ordering contains expressions.

[Django]

#30557: order_by() a parent model crash when Meta.ordering contains expressions.
-+-
 Reporter:  Jonny Fuller |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  ordering | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by GitHub ):

 In [changeset:"7a42cfcfdc94c1e7cd653f3140b9eb30492bae4f" 7a42cfcf]:
 {{{
 #!CommitTicketReference repository=""
 revision="7a42cfcfdc94c1e7cd653f3140b9eb30492bae4f"
 Refs #30557 -- Fixed crash of ordering by ptr fields when Meta.ordering
 contains F() expressions.

 Thanks Can Sarıgöl for the report.

 Follow up to 8c5f9906c56ac72fc4f13218dd90bdf9bc8a248b.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.5f700043b2cae9e38867b9d6f790e998%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23004: Cleanse entries from request.META in debug views

[Django]

#23004: Cleanse entries from request.META in debug views
-+-
 Reporter:  Daniel Hahler|Owner:  Daniel Maxson
 Type:  New feature  |   Status:  assigned
Component:  Error reporting  |  Version:  master
 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 Carlton Gibson):

 OK... Right...

 First off, thank you everybody for input on this (and related tickets).

 I say "and related tickets" because this kind of thing keeps coming up.
 (e.g. #23951 but others) ''Can we filter this?'', ''Can we filter that?'',
 and so on.

 #29714 suggests making having a custom `ExceptionReporter` easier. In this
 case you'd just override `get_traceback_data()` and job done. I'm hoping
 to get that in.

 There was [https://code.djangoproject.com/ticket/25167#comment:1 an idea
 to get rid of the exception filter as the extension point] but I think
 that's too quick for now. **As such**, I'd like to go for the more
 ambitious of the two approaches here. I think
 [https://code.djangoproject.com/ticket/23004#comment:2 Tim's original
 comment, way back when] was the right one in terms of providing the right
 flexibility without us having to add hooks for every possible use-case.

 On that basis, I'm going to close Markus' PR (Thank you again Markus) and
 then have one final look... I hope that makes sense.

 > ...especially considering that this is a DEBUG=True.

 It's not. `ExceptionReporter` is used `AdminEmailHandler` at the least.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.69182feae0406853aadd5fae312836cf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23951: SafeExceptionReporterFilter does not have a way to filter and redact exception messages

[Django]

#23951: SafeExceptionReporterFilter does not have a way to filter and redact
exception messages
-+
 Reporter:  Lukhnos Liu  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Error reporting  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  logging  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Carlton Gibson):

 Arguably this would be resolved by a fix to #29714 (for which there's an
 open PR): users could implement a custom exception reporter to filter as
 they needed, rather than us adding logic for each possible exclusion use-
 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.cf2d6b6cad10f1bd7a325173ce23872a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29714: Make it easier to customise ExceptionReporter output.

[Django]

#29714: Make it easier to customise ExceptionReporter output.
-+-
 Reporter:  Vasili Korol |Owner:  Nasir
 |  Hussain
 Type:  New feature  |   Status:  assigned
Component:  Error reporting  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  email, reports,  | Triage Stage:  Accepted
  cookies|
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1
 * needs_docs:  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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.087e16458ea5aff1a2a2e75d39544f82%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30557: order_by() a parent model crash when Meta.ordering contains expressions.

[Django]

#30557: order_by() a parent model crash when Meta.ordering contains expressions.
-+-
 Reporter:  Jonny Fuller |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  ordering | 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:"8c5f9906c56ac72fc4f13218dd90bdf9bc8a248b" 8c5f9906]:
 {{{
 #!CommitTicketReference repository=""
 revision="8c5f9906c56ac72fc4f13218dd90bdf9bc8a248b"
 Fixed #30557 -- Fixed crash of ordering by ptr fields when Meta.ordering
 contains expressions.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.d950972bb899d54bb638ae176c13d8a3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30632: Pagination for FormSet

[Django]

#30632: Pagination for FormSet
-+---
 Reporter:  Parth Patil  |Owner:  Parth Patil
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  2.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+---

Comment (by felixxm):

 I don't see any benefit in using a paginated formset in this scenario,
 because you will be able to work only on a single page i.e. only with a
 subset of forms from formset. It's not necessary to create formset with
 100 forms to use only 10 of them. You should rather paginate a queryset
 and create formset for a single page.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.afbc4e399d49e11a816d74eb02ec6479%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30632: Pagination for FormSet

[Django]

#30632: Pagination for FormSet
-+---
 Reporter:  Parth Patil  |Owner:  Parth Patil
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  2.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+---

Comment (by Carlton Gibson):

 Hey Parth.

 > Mostly for e.g. blog sites if there are 100 blog models…

 In this case don’t you paginate the queryset prior to creating the
 FormSet?

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.75d542fdb34f83a4ce6cce4aef7e2829%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30632: Pagination for FormSet

[Django]

#30632: Pagination for FormSet
-+---
 Reporter:  Parth Patil  |Owner:  Parth Patil
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  2.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+---

Comment (by Parth Patil):

 Replying to [comment:2 felixxm]:
 > Can you describe the use case and your motivation? I'm not sure how it
 would work. "Normally" you will lose all entered data after changing a
 page.

 I intended it to be used for model formsets. Mostly for e.g. blog sites if
 there are 100 blog models on can easily have it paginated and well
 formatted using formsets while also selecting which fields to show.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.9e04ab9d26ea282e1a8b5128cec74785%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30411: Improve traceback formatting in technical 500 text responses

[Django]

#30411: Improve traceback formatting in technical 500 text responses
--+
 Reporter:  Daniel Hahler |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Error reporting   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Carlton Gibson):

 * status:  assigned => new
 * owner:  Daniel Hahler => (none)


Comment:

 Deassigning due to inactivity.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.7cd34e18e4e934981517265a74c4fbf9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30632: Pagination for FormSet

[Django]

#30632: Pagination for FormSet
-+---
 Reporter:  Parth Patil  |Owner:  Parth Patil
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  2.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+---

Comment (by felixxm):

 Can you describe the use case and your motivation? I'm not sure how it
 would work. "Normally" you will lose all entered data after changing a
 page.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.6efa9eb7bcaf8e1d8b2e5149b8998ad1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30632: Pagination for FormSet

[Django]

#30632: Pagination for FormSet
-+---
 Reporter:  Parth Patil  |Owner:  Parth Patil
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  2.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+---
Changes (by Parth Patil):

 * owner:  nobody => Parth Patil
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 Here is a PR for the new feature
 https://github.com/django/django/pull/11558

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.360d1bfedee2827d2879243caee652b6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #30632: Pagination for FormSet

[Django]

#30632: Pagination for FormSet
---+
   Reporter:  Parth Patil  |  Owner:  nobody
   Type:  New feature  | Status:  new
  Component:  Forms|Version:  2.2
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  1
  UI/UX:  0|
---+
 Having pagination directly built into ``FormSet`` will really be a nice
 shortcut for users. This will enable people to use formset with more
 versatility. For e.g. can benefit from this.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.daa3a8aa5768b90ba3de3e393ad59e40%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23004: Cleanse entries from request.META in debug views

[Django]

#23004: Cleanse entries from request.META in debug views
-+-
 Reporter:  Daniel Hahler|Owner:  Daniel Maxson
 Type:  New feature  |   Status:  assigned
Component:  Error reporting  |  Version:  master
 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
-+-
Description changed by Carlton Gibson:

Old description:



New description:

 In the debug views `settings` is cleansed, which hides e.g. `SECRET_KEY`.

 But a lot of sensible information might also be present / come from
 `request.META`, e.g. in the form of `DJANGO_SECRET_KEY` or `DATABASE_URL`.

 It might be sensible to apply a filter in `TECHNICAL_500_TEMPLATE` (source
 code reference:
 https://github.com/django/django/blob/master/django/views/debug.py#L972-977).

 I see that this can be quite specific, but I think it would be sensible to
 apply `HIDDEN_SETTINGS` to all entries starting with `DJANGO_` and have a
 setting for additional entries, which might default to `DATABASE_URL` and
 `SENTRY_DSN`.

--

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.f5620a745fa31c33e0269d3d944f72f0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28289: QuerySet.count() does not with work raw sql annotations on inherited model fields

[Django]

#28289: QuerySet.count() does not with work raw sql annotations on inherited 
model
fields
-+-
 Reporter:  Karolis Ryselis  |Owner:  Can
 |  Sarıgöl
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"52545e788d664040abf4f1a5d77cdfc61152ffca" 52545e7]:
 {{{
 #!CommitTicketReference repository=""
 revision="52545e788d664040abf4f1a5d77cdfc61152ffca"
 Fixed #28289 -- Fixed crash of RawSQL annotations on inherited model
 fields.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.8075e58aefb0b7f859f99dc52170ae9d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30557: order_by() a parent model crash when Meta.ordering contains expressions.

[Django]

#30557: order_by() a parent model crash when Meta.ordering contains expressions.
-+-
 Reporter:  Jonny Fuller |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ordering | 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):

 * status:  new => assigned
 * needs_better_patch:  1 => 0
 * owner:  (none) => Hasan Ramezani


Comment:

 [https://github.com/django/django/pull/11555 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.73dee8793bf373cc8e7a1216e21d92a9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.