Re: [Django] #28201: Make CharField form field prohibit null characters

[Django]

#28201: Make CharField form field prohibit null characters
-+-
 Reporter:  CM Lubinski  |Owner:  Alejandro
 Type:   |  Zamora Fonseca
  Cleanup/optimization   |   Status:  assigned
Component:  Forms|  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 Claude Paroz):

 * needs_better_patch:  1 => 0


--
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.86aaf8c8bdabc777498665a6d9e36f06%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22229: Invalid data can cause InlineFormSet.is_valid to throw ValueError

[Django]

#9: Invalid data can cause InlineFormSet.is_valid to throw ValueError
-+-
 Reporter:  anonymous|Owner:  Jake
 |  Rothenbuhler
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  InlineFormSet| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jon Dufresne):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/8679 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/067.c596191b223eb6777ebd58a7516ab442%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22841: ModelChoiceField does not make it easy to reuse querysets

[Django]

#22841: ModelChoiceField does not make it easy to reuse querysets
-+
 Reporter:  Marc Tamlyn  |Owner:  Michael Vasiliou
 Type:  New feature  |   Status:  assigned
Component:  Forms|  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 Michael Vasiliou):

 * owner:  nobody => Michael Vasiliou
 * 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 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/066.25abe4cd4bd418b56524fffc7d764aff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #14204: Take advantage of SQLite support for FK constraints

[Django]

#14204: Take advantage of SQLite support for FK constraints
-+-
 Reporter:  Ramiro Morales   |Owner:  Claude
 |  Paroz
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  sqlite, foreign key  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 I've worked on updating Claude's patch by incorporating Simon's suggestion
 of adding `DEFERRABLE INITIALLY DEFERRED`:
 [https://github.com/django/django/pull/8678 PR]

 There are still some issues to figure out.

--
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/064.18b8ab5cb3dec741e8ee9569662911c0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28331: Add an extra_context attribute to class-based generic views that use ContextMixin (e.g. TemplateView)

[Django]

#28331: Add an extra_context attribute to class-based generic views that use
ContextMixin (e.g. TemplateView)
-+-
 Reporter:  Jeremy   |Owner:  Bruno
 Type:   |  Alla
  Cleanup/optimization   |   Status:  assigned
Component:  Generic views|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_docs:  0 => 1
 * has_patch:  0 => 1


Comment:

 The [https://github.com/django/django/pull/8671 PR] is missing
 documentation. See the PatchReviewChecklist.

--
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.cf3ee3b29613f61ef046e44771c2fd5c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28313: Add a contenttypes check to prohibit model names greater than 100 characters

[Django]

#28313: Add a contenttypes check to prohibit model names greater than 100
characters
-+-
 Reporter:  Michal Dabski|Owner:  Tim
 Type:   |  Graham 
  Cleanup/optimization   |   Status:  closed
Component:   |  Version:  1.11
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  contenttype, model,  | Triage Stage:  Accepted
  name, length, migration|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * owner:  (none) => Tim Graham 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"d381914aef50e04ca44b9d7bb9274c8351f5b9bf" d381914]:
 {{{
 #!CommitTicketReference repository=""
 revision="d381914aef50e04ca44b9d7bb9274c8351f5b9bf"
 Fixed #28313 -- Added model name max length check of 100 characters in
 contrib.contentttypes.
 }}}

--
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/064.99a6ad745750b8dcd7cc33982bf12d01%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28339: Setting db_index=False on a field doesn't actually remove the index

[Django]

#28339: Setting db_index=False on a field doesn't actually remove the index
--+--
 Reporter:  Craig de Stigter  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Migrations|  Version:  1.11
 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
--+--
Changes (by Craig de Stigter):

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


Comment:

 On second thoughts, this is still a bug, right?

 sqlmigrate above shows that the operation creating the indices _knows_ the
 name of the indices:

 {{{
 #!sql
 CREATE INDEX "a_b_charfield_a5049317" ON "a_b" ("charfield");
 }}}

 so clearly this can be predicted up-front by the migration - it shouldn't
 need to consult the database to list indices prior to dropping them.

--
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.16619654025a39d83631ae25304e9dbf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28313: Add a contenttypes check to prohibit model names greater than 100 characters

[Django]

#28313: Add a contenttypes check to prohibit model names greater than 100
characters
-+-
 Reporter:  Michal Dabski|Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:   |  Version:  1.11
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:
 Keywords:  contenttype, model,  | Triage Stage:  Accepted
  name, length, migration|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Michal Dabski):

 * owner:  Michal Dabski => (none)
 * status:  assigned => new


--
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/064.2efacd15363de6847fd71b4cf9fdaffb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28294: Document request/args/kwargs attributes of class-based views

[Django]

#28294: Document request/args/kwargs attributes of class-based views
-+-
 Reporter:  Tony Narlock |Owner:  Michael
 Type:   |  Vasiliou
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:  documentation views  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/8674 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/062.3e874111c4da760c0efc2be6dfab74aa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28201: Make CharField form field prohibit null characters (was: Make CharField/TextField prohibit null characters)

[Django]

#28201: Make CharField form field prohibit null characters
-+-
 Reporter:  CM Lubinski  |Owner:  Alejandro
 Type:   |  Zamora Fonseca
  Cleanup/optimization   |   Status:  assigned
Component:  Forms|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 Correct, there's isn't a  `TextField` form field.

--
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.bd6060f3982aea862223f14fe8d7e15a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27964: Raise an error if a MySQL geometry with an unsupported SRID is saved to the database

[Django]

#27964: Raise an error if a MySQL geometry with an unsupported SRID is saved to 
the
database
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  closed
Component:  GIS  |  Version:  1.8
 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 Tim Graham ):

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


Comment:

 In [changeset:"44a7b98abbec02f1a4f35662040f602fd616d0cd" 44a7b98a]:
 {{{
 #!CommitTicketReference repository=""
 revision="44a7b98abbec02f1a4f35662040f602fd616d0cd"
 Fixed #27964 -- Made MySQL backend raise exception if spatial
 transformation is needed for query.
 }}}

--
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.d03f3a423b8243b601f373f79dadfb12%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28297: Same queryset result in two different queries on ORM

[Django]

#28297: Same queryset result in two different queries on ORM
-+-
 Reporter:  Marcus Renno |Owner:  Marcus
 |  Renno
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  join, annotation, F  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1


Comment:

 As noted on the PR, I'm not sure that the current approach is ideal.

--
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/069.52be1fa8bdf6f78a9628bdff5021dbbf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26362: Manually changing the parent of a child model is silently failing.

[Django]

#26362: Manually changing the parent of a child model is silently failing.
-+-
 Reporter:  Keith Hostetler  |Owner:  Paulo
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (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 Tim Graham ):

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


Comment:

 In [changeset:"c4329271607637373e42f081bd632e653aa99ea3" c4329271]:
 {{{
 #!CommitTicketReference repository=""
 revision="c4329271607637373e42f081bd632e653aa99ea3"
 Fixed #26362 -- Fixed update of the inherited id field of an object when
 its parent changes.
 }}}

--
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.4ba3657b5c30568cd6ebdd511c24fae5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24823: FileField with callable default raises error with forms (was: FileField with callable default raise error with forms)

[Django]

#24823: FileField with callable default raises error with forms
-+-
 Reporter:  Haussonne Yves-  |Owner:  nobody
  Marie  |
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  FileField, models,   | Triage Stage:  Accepted
  field, callable, default, form |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * 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 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/062.6ce5d7d353c8a7620d84ae178f240200%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28335: Add query expressions support for models meta ordering

[Django]

#28335: Add query expressions support for models meta ordering
-+-
 Reporter:  cypreess |Owner:  Dima
 |  Kudosh
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  model ordering F | Triage Stage:
  query expressions  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

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


Comment:

 Duplicate of #26257

--
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/066.a9cad4035ce2c7eff3cc58386d990543%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28337: fetch_redirect_response from assertRedirects doesn't honor HTTP_HOST setting in self.client.get

[Django]

#28337: fetch_redirect_response from assertRedirects doesn't honor HTTP_HOST
setting in self.client.get
--+
 Reporter:  Roland van Laar   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  Version:  1.11
 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 Tim Graham):

 * type:  Bug => Cleanup/optimization
 * 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 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/066.b437eb62073c03d9eefbe51cffa80e80%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23919: Cleanups for when we drop Python 2 compatibility

[Django]

#23919: Cleanups for when we drop Python 2 compatibility
--+
 Reporter:  Tim Graham|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:
 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 Tim Graham ):

 In [changeset:"081e78716085ff4af08604af5d084c8fd27c0730" 081e787]:
 {{{
 #!CommitTicketReference repository=""
 revision="081e78716085ff4af08604af5d084c8fd27c0730"
 Refs #23919 -- Stopped inheriting from object to define new style classes.

 Tests and docs complement to cecc079168e8669138728d31611ff3a1e7eb3a9f.
 }}}

--
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.8056d871dc28709fb462fccaed1d35a8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28201: Make CharField/TextField prohibit null characters

[Django]

#28201: Make CharField/TextField prohibit null characters
-+-
 Reporter:  CM Lubinski  |Owner:  Alejandro
 Type:   |  Zamora Fonseca
  Cleanup/optimization   |   Status:  assigned
Component:  Forms|  Version:  1.11
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Alejandro Zamora Fonseca):

 Maybe only adding the  null char validator to CharField would be enough?
 Because TextField is converted to CharField when Model to Field
 translation occurs.

--
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.f0abfa80cac60a92f13669a31d34a182%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28334: contrib.postgresql overwhelms database with "select from pg_type" queries on each request

[Django]

#28334: contrib.postgresql overwhelms database with "select from pg_type" 
queries
on each request
-+-
 Reporter:  Igor Gumenyuk|Owner:  Igor
 Type:   |  Gumenyuk
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.postgres |  Version:  1.11
 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 Igor Gumenyuk):

 * status:  new => assigned
 * owner:  (none) => Igor Gumenyuk


--
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/064.5019e6e717f4a46a59151fb46bfc9b29%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27964: Raise an error if a MySQL geometry with an unsupported SRID is saved to the database

[Django]

#27964: Raise an error if a MySQL geometry with an unsupported SRID is saved to 
the
database
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Sergey
 Type:   |  Fedoseev
  Cleanup/optimization   |   Status:  assigned
Component:  GIS  |  Version:  1.8
 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 Sergey Fedoseev):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/8676 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/068.21e09f6984d94fe418adcd01a3d4a3e0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28340: USE_THOUSAND_SEPARATOR=True causes primary key to include commas

[Django]

#28340: USE_THOUSAND_SEPARATOR=True causes primary key to include commas
-+-
 Reporter:  Zach Borboa  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 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 Zach Borboa):

 Can this behavior be documented with a note?

 {{{
 diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt
 index 70402b1fc4..c5d83c38a8 100644
 --- a/docs/ref/settings.txt
 +++ b/docs/ref/settings.txt
 @@ -2669,6 +2669,12 @@ format, it will have higher precedence and will
 be applied instead.
 See also :setting:`DECIMAL_SEPARATOR`, :setting:`NUMBER_GROUPING` and
 :setting:`THOUSAND_SEPARATOR`.

 +.. note::
 +
 +Using ``{{ object.pk }}`` and ``{{ object.id }}`` may include
 +:setting:`THOUSAND_SEPARATOR`. Consider using {{
 object.pk|unlocalize }}
 +instead.
 +
 .. setting:: USE_TZ

 ``USE_TZ``
 }}}

--
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.4c4bc93ee116e2aef2510c24b54a375b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28340: USE_THOUSAND_SEPARATOR=True causes primary key to include commas

[Django]

#28340: USE_THOUSAND_SEPARATOR=True causes primary key to include commas
-+-
 Reporter:  Zach Borboa  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 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 Tim Graham):

 * status:  new => closed
 * resolution:   => wontfix
 * component:  Uncategorized => Template system
 * type:  Uncategorized => Cleanup/optimization


Comment:

 Use the
 [https://docs.djangoproject.com/en/dev/topics/i18n/formatting/#unlocalize
 unlocalize] template filter, e.g. `{% load l10n %} {{ obj.pk|unlocalize
 }}`. I don't think some automatic behavior would be desirable considering
 there could be cases where you want a localized value.

--
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.4e0fa8eceb142c771132ebdc1de5cc1e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28340: USE_THOUSAND_SEPARATOR=True causes primary key to include commas

[Django]

#28340: USE_THOUSAND_SEPARATOR=True causes primary key to include commas
-+
   Reporter:  Zach Borboa|  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  master
   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  |
-+
 When {{{USE_THOUSAND_SEPARATOR=True}}}, an object's primary key (pk) and
 identifier (id) fields unexpectedly include commas when used in templates.

 Example:
 Say I include {{{}}} in a
 template with a submit button to save an article, saves will eventually
 fail {{{QuerySet.get(pk='1,000')}}} containing a comma. Using {{{ {{
 object.pk }} }}} in a template will initially work, but later fail when
 the 1000th entry is saved.

 Possible solution: Display numbers using a thousand separator when
 {{{USE_THOUSAND_SEPARATOR=True}}}, except for an object's pk and object's
 id fields as these are understood to be keys and identifiers,
 respectively.

--
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.4ba3b0cb5d74f1f0c67dec76f3eba66c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28297: Same queryset result in two different queries on ORM

[Django]

#28297: Same queryset result in two different queries on ORM
-+-
 Reporter:  Marcus Renno |Owner:  Marcus
 |  Renno
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  join, annotation, F  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Jeppe Vesterbæk):

 * cc: jeppe@… (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 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/069.f1ee7189b9df8b7755633e1a386a8724%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.