Re: [Django] #25789: Inefficient Queries Generated due to not using WHERE EXISTS

[Django]

#25789: Inefficient Queries Generated due to not using WHERE EXISTS
-+-
 Reporter:  Alex Rothberg|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 James, since this ticket was filled support for `Exists` expression was
 added so you should be able to avoid using `extra`

 {{{#!python
 queryset.annotate(
 foo_exists=Exists(subqueryset.filter(foo_id=OuterRef('pk'))
 ).filter(
 foo_exists=False,
 )
 }}}

 Once #25367 lands it'll be possible to pass `~Exists` directly to filter.

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

Re: [Django] #29680: Paginate start with last Page

[Django]

#29680: Paginate start with last Page
-+-
 Reporter:  Dario Navin  |Owner:  Dario
 Type:   |  Navin
  Cleanup/optimization   |   Status:  assigned
Component:  Generic views|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 I'm afraid I'm still not following. All the URLs you gave have `page=X`
 and if I remove that, I get the first page. I thought the idea was that
 you wanted a URL without `page=X` to show the last page? It looks like
 #4919 was implemented to allow `?page=last`  to do what you want.

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

Re: [Django] #29681: Support XHTML5 (XML serialization of HTML5)

[Django]

#29681: Support XHTML5 (XML serialization of HTML5)
-+-
 Reporter:  Nils Fredrik |Owner:  nobody
  Gjerull|
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Forms|  Version:  2.1
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  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
 * type:  Uncategorized => Cleanup/optimization


Comment:

 The [https://groups.google.com/d/topic/django-
 developers/G4Rz1_Bmh7w/discussion django-developers discussion] hasn't
 yielded a consensus to make this change. As I said on the mailing list,
 please look into
 [https://docs.djangoproject.com/en/stable/ref/forms/renderers/ custom
 widget templates] for 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/061.e9b58e3c47f1f7ae667c7b8f846f09b0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29678: inspectdb fails on MySQL 8 with " 'utf8' is currently an alias for the character set UTF8MB3"

[Django]

#29678: inspectdb fails on MySQL 8 with " 'utf8' is currently an alias for the
character set UTF8MB3"
-+-
 Reporter:  SuilAmhain   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  2.1
  commands)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by SuilAmhain):

 If I connect to the DB from python shell and execute basically the same
 commands, I can see that Mysql connector is defaulting
 {{{raise_on_warnings}}} to {{{False}}}

 If I manually set {{{raise_on_warnings}}} to {{{True}}} I then get the
 same error as from within inspectdb.

 I honestly do not know where the responsibility lies for the bug or where
 {{{raise_on_warnings}}} is getting changed within the Django stack.

 Anyways hopefully this note helps somebody somewhere at some stage :-)

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

[Django] #29681: Support XHTML5 (XML serialization of HTML5)

[Django]

#29681: Support XHTML5 (XML serialization of HTML5)
+
   Reporter:  Nils Fredrik Gjerull  |  Owner:  nobody
   Type:  Uncategorized | Status:  new
  Component:  Forms |Version:  2.1
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 Frameworks and libraries that generate html should output well-formed html
 that can be used for both HTML serialization (text/html) and XML
 serialization (application/xhtml+xml). This implies that Django should
 continue to output XML compatible markup even for HTML5.

 This do not mean that Django need to be restricted by the XHTML-
 Transitional and XHTML-Strict standard. It only means that HTML5 needs to
 be written in a XML compatible style.

 This affects Django in three ways:
 1. HTML must be well-formed. All start-tags needs an end-tag (except self-
 closing tags). This is already the case.
 1. All self-closing tags must end with '/>'.
 2. All boolean attributes must have a value e.g 'checked="checked"'.

 I will say that this time is the best time ever to serve pages with
 application/xhtml+xml, because all browsers supports it. IE was the road
 blocker for year, but since IE9 it supports it as well. Se a list of the
 [https://developer.mozilla.org/en-
 US/docs/Web/HTTP/Content_negotiation/List_of_default_Accept_values default
 value of the Accept header] for various browsers from Mozilla.

 See:
 * [https://www.w3.org/TR/html/introduction.html#html-vs-xhtml]
 * [https://www.w3.org/TR/html/the-xhtml-syntax.html]
 * [https://en.wikipedia.org/wiki/HTML5#XHTML_5_(XML-serialized_HTML_5)]

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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/046.d3636fd84a28e9d75ad4813f64e5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29678: inspectdb fails on MySQL 8 with " 'utf8' is currently an alias for the character set UTF8MB3"

[Django]

#29678: inspectdb fails on MySQL 8 with " 'utf8' is currently an alias for the
character set UTF8MB3"
-+-
 Reporter:  SuilAmhain   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  2.1
  commands)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by SuilAmhain):

 * Attachment "2018-08-16 23_28_15-Exploration
 [C__Users_user01_Documents_Open University_TM470_TM470PyCharmProject.png"
 added.

 Fully Worked Example in Python Shell without Django wrapping MySQL
 Connector

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

Re: [Django] #29680: Paginate start with last Page

[Django]

#29680: Paginate start with last Page
-+-
 Reporter:  Dario Navin  |Owner:  Dario
 Type:   |  Navin
  Cleanup/optimization   |   Status:  assigned
Component:  Generic views|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Dario Navin):

 Here are some examples which use the pagination I described:

 1. https://ubuntuforums.org/showthread.php?t=2015424&page=8
 2. https://www.wallstreetoasis.com/forums/2019-ft-analyst-recruiting-
 timeline?page=1
 3. https://python-forum.io/Thread-Enigma-Machine-I-need-help?page=7

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

Re: [Django] #29680: Paginate start with last Page

[Django]

#29680: Paginate start with last Page
-+-
 Reporter:  Dario Navin  |Owner:  Dario
 Type:   |  Navin
  Cleanup/optimization   |   Status:  assigned
Component:  Generic views|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 Maybe I'm missing the point, but I don't recall a forum that used the type
 of pagination you describe. It doesn't seem intuitive. Pages are sorted
 from newest to oldest but the items within the page are sorted from oldest
 to newest?

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

Re: [Django] #29678: inspectdb fails on MySQL 8 with " 'utf8' is currently an alias for the character set UTF8MB3"

[Django]

#29678: inspectdb fails on MySQL 8 with " 'utf8' is currently an alias for the
character set UTF8MB3"
-+-
 Reporter:  SuilAmhain   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  2.1
  commands)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * resolution:  worksforme => invalid


Comment:

 Thanks for investigating. So it seems to be an issue with MySQL
 Connector/Python and Django isn't at fault.

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

Re: [Django] #29646: Document the validators that each model and form field uses

[Django]

#29646: Document the validators that each model and form field uses
-+-
 Reporter:  Shrey Batra  |Owner:  Jeff
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"91af869d701c7f7f34a8aed834791bf5c9fb3d07" 91af869d]:
 {{{
 #!CommitTicketReference repository=""
 revision="91af869d701c7f7f34a8aed834791bf5c9fb3d07"
 [2.1.x] Fixed #29646 -- Doc'd the validators that each model and form
 field uses.

 Backport of 3fa3de54152a6b7a67de05ff4ff6fb122c9246e2 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 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.830e30878e50491e82e163cae53726e0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29646: Document the validators that each model and form field uses

[Django]

#29646: Document the validators that each model and form field uses
-+-
 Reporter:  Shrey Batra  |Owner:  Jeff
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"3fa3de54152a6b7a67de05ff4ff6fb122c9246e2" 3fa3de5]:
 {{{
 #!CommitTicketReference repository=""
 revision="3fa3de54152a6b7a67de05ff4ff6fb122c9246e2"
 Fixed #29646 -- Doc'd the validators that each model and form field uses.
 }}}

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

Re: [Django] #29678: inspectdb fails on MySQL 8 with " 'utf8' is currently an alias for the character set UTF8MB3"

[Django]

#29678: inspectdb fails on MySQL 8 with " 'utf8' is currently an alias for the
character set UTF8MB3"
-+-
 Reporter:  SuilAmhain   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  2.1
  commands)  |   Resolution:
 Severity:  Normal   |  worksforme
 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 SuilAmhain):

 I have found a workaround of sorts.
 For the record:
 - mysql-connector-python=8.0.12
 - I have just moved the MySQL instance from 8.0.11 to 8.0.12
 - django 2.1

 I have tried various settings passed to the database via {{{settings.py}}}
 but getting nowhere with them, for example:

 {{{
 DATABASES = {
 'default': {
 'ENGINE': 'mysql.connector.django',
 #'ENGINE': 'django.db.backends.mysql',
 'NAME': '',
 'USER': '',
 'PASSWORD': '',
 'HOST': '',
 'CHARSET': 'utf8mb4',
 'COLLATION': 'utf8mb4_unicode_ci',
 'PORT': '3309',
 'OPTIONS': {'sql_mode': 'TRADITIONAL', 'use_pure': True,
 'use_unicode': True, 'charset': 'utf8mb4',
 'collation':
 'utf8mb4_general_ci','get_warnings':False},
 }
 }}}

 MySQL connector docs state that {{{raise_on_warnings}}} defaults to
 {{{False}}}. It is however getting set to true somewhere in the code.
 - https://dev.mysql.com/doc/connector-python/en/connector-python-api-
 mysqlconnection-raise-on-warnings.html

 In {{{site-packages -> mysql -> connector -> cursor.py}}} I changed the
 last few lines of the {{{execute}}} function to:

 {{{
 if multi:
 self._executed_list = []
 return
 self._execute_iter(self._connection.cmd_query_iter(stmt))
 exlcude_schema=b'information_schema' # New COS Workaround
 if exlcude_schema in stmt:   # New COS Workaround
 print(self._connection.get_warnings) # New COS Workaround
 self._connection.get_warnings = False# New COS Workaround
 try:
 self._handle_result(self._connection.cmd_query(stmt))
 except errors.InterfaceError:
 if self._connection._have_next_result:  # pylint:
 disable=W0212
 raise errors.InterfaceError(
 "Use multi=True when executing multiple statements")
 raise
 return None
 }}}

 It is not very elegant, but I am rushing for a college deadline and well
 time is ticking.

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

Re: [Django] #29680: Paginate start with last Page

[Django]

#29680: Paginate start with last Page
-+-
 Reporter:  Dario Navin  |Owner:  Dario
 Type:   |  Navin
  Cleanup/optimization   |   Status:  assigned
Component:  Generic views|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Dario Navin):

 Replying to [comment:1 Tim Graham]:
 > What's the use case for starting pagination on the last page? Couldn't
 you just reverse the order of whatever you're paginating?

 Forums use the same schema as well as displaying messages.

 Let's say I have a simple Message model.



 I want to display my messages with the latest message being on the bottom:

 1. First Message
 2. Second Message
 3. 
 4. Latest Message

 In the current state I would have to order the queryset decending by id in
 my view to get the last message on the first page.



 {{{
 class SingleMessageDetailView(ListView):
 model = Message
 template_name = 'message.html'
 paginate_by = 10
 context_object_name = "messages"
 ordering = "-id"
 }}}

 But now I am facing the problem that the last message is the first object
 in my queryset.
 I could solve it by reversing the queryset in the template but in my
 opinion that is not a beautiful code since we have to make two adjustments
 at two different ends.


 {{{
 {% for obj in messages reversed %}
 }}}


 Having the option to start at the last page would make it easier &
 friendlier for development.

 The other current option is to use a function based view or to change the
 url:


 {{{
 # Normally I would move the 'page last part' to the absolute url but for
 demonstration purpose I have put it in the html code.
 {{ message.subject
 }}
 }}}


 Also, jumping to the last page is quite common in forums and follows the
 "book-style".

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

Re: [Django] #29656: Range Fields do not support blank values via ModelForm

[Django]

#29656: Range Fields do not support blank values via ModelForm
--+--
 Reporter:  James Addison |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:  duplicate
 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 James Addison):

 Tim, Carlton,

 I have little choice but to keep a hack in place (marked with a ''TODO''
 note to revisit in future, of course). I don't particularly have a problem
 with this, but would like to see consistency and a better user experience
 for this in Django.

 I'll bring it up on the mailing list, as you recommend. For the most part,
 I'll leave it in your hands after that, unless people ask me for feedback.

 Thanks again.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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.09a0331a616e06a3fcc96ffd279dbc6b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29656: Range Fields do not support blank values via ModelForm

[Django]

#29656: Range Fields do not support blank values via ModelForm
--+--
 Reporter:  James Addison |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:  duplicate
 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 Tim Graham):

 I'm not sure if there's a model field in Django where there's a chance for
 two values that could be considered "empty" besides `CharField` and the
 range fields. The docs for `Field.null` say, "In most cases, it’s
 redundant to have two possible values for “no data;” the Django convention
 is to use the empty string, not NULL." I'm not sure if there was much
 consideration of null vs. empty range for range field but changing it as
 this point merits a discussion on the DevelopersMailingList.

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

Re: [Django] #29656: Range Fields do not support blank values via ModelForm

[Django]

#29656: Range Fields do not support blank values via ModelForm
--+--
 Reporter:  James Addison |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.postgres  |  Version:  master
 Severity:  Normal|   Resolution:  duplicate
 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 Carlton Gibson):

 Hey James. It’s late for me now so I can’t address each point you make
 individually. I will though make time to go over this again just to be
 sure.

 Right now I’ll just say that I think this issue is a symptom of the more
 general problem that HTML forms don’t distinguish properly between empty
 string submissions when you mean empty string and empty string submissions
 when you mean None. (Or with checkboxes, not submitted vs false.) As such
 Django forms have to do their best to behave sensibly in the widest number
 of cases. (It’s been many years getting to where it is now: not that it
 can’t be improved but it’s pretty battle tested.)

 In your case you have a form with a different requirement, but I think
 you’ll need to add that logic yourself.

 As I said, I will though, have another think about this one.

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

Re: [Django] #29680: Paginate start with last Page

[Django]

#29680: Paginate start with last Page
-+-
 Reporter:  Dario Navin  |Owner:  Dario
 Type:   |  Navin
  Cleanup/optimization   |   Status:  assigned
Component:  Generic views|  Version:  2.1
 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 Tim Graham):

 * easy:  1 => 0


Comment:

 What's the use case for starting pagination on the last page? Couldn't you
 just reverse the order of whatever you're paginating?

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

[Django] #29680: Paginate start with last Page

[Django]

#29680: Paginate start with last Page
-+-
   Reporter:  Dario  |  Owner:  Dario Navin
  Navin  |
   Type: | Status:  assigned
  Cleanup/optimization   |
  Component:  Generic|Version:  2.1
  views  |
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 Hi,

 currently you can't set the paginate to start with the last page if no
 page is given unless you put in the url.

 MultipleObjectMixin:
 {{{
 page_kwarg = self.page_kwarg
 # I suggest removing the static 1 and replace it with a function
 called
 # get_start_page whose default return value is 1
 page = self.kwargs.get(page_kwarg) or
 self.request.GET.get(page_kwarg) or 1
 try:
 page_number = int(page)
 except ValueError:
 if page == 'last':
 page_number = paginator.num_pages
 else:
 raise Http404(_("Page is not 'last', nor can it be
 converted to an int."))
 }}}

 Suggested change:

 {{{
 page = self.kwargs.get(page_kwarg) or self.request.GET.get(page_kwarg) or
 self.get_start_page()
 }}}

 Default would be 1. Then for starting with the last page someone could set
 it to

 {{{
 def get_start_page(self):
return self.get_paginator().num_pages
 }}}


 I did search but could not find any report about it.

 If someone could approve this, I would submit a fix.

 Best regards,

 Dario Heinisch

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

[Django] #29679: select_related not working as expected with Oracle 12C and Python 3.6

[Django]

#29679: select_related not working as expected with Oracle 12C and Python 3.6
-+-
   Reporter:  zap_kid|  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.1
  layer (models, ORM)|   Keywords:  orm, oracle,
   Severity:  Normal |  select_related
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Suppose I have `ModelA` and `ModelB` where `ModelA` has a `ForeignKey`
 field `model_b` with `ModelB` and in addition `ModelA` and `ModelB` share
 another non-foreign key field with the same name. Then
 `ModelA.objects.filter(...).select_related('model_b')` throws
 `django.db.utils.DatabaseError: ORA-00918: column ambiguously defined`
 even though Django is generating the correct `SQL`.  See
 [https://stackoverflow.com/questions/51879477/django-2-1-and-select-
 related]

 discovered using Oracle 12C and Python 3.6

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

Re: [Django] #8936: Add view (read-only) permission to admin

[Django]

#8936: Add view (read-only) permission to admin
-+-
 Reporter:  simon|Owner:  Olivier
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"cd790ed1a6dbdf910c41da44c306ddae6ea6fd4d" cd790ed1]:
 {{{
 #!CommitTicketReference repository=""
 revision="cd790ed1a6dbdf910c41da44c306ddae6ea6fd4d"
 Refs #8936 -- Added ModelAdmin.has_view_or_change_permission().
 }}}

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

Re: [Django] #29654: Truncate should use horizontal ellipsis character instead of three dots

[Django]

#29654: Truncate should use horizontal ellipsis character instead of three dots
--+
 Reporter:  Sudhanshu Mishra  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:  string, truncator | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Ove Lindström):

 I updated the test cases and the .po -files in PR
 https://github.com/django/django/pull/10306

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

Re: [Django] #25789: Inefficient Queries Generated due to not using WHERE EXISTS

[Django]

#25789: Inefficient Queries Generated due to not using WHERE EXISTS
-+-
 Reporter:  Alex Rothberg|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by James Howe):

 * cc: James Howe (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/067.6ba36fa3245d73e3743c7d23930d9298%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25789: Inefficient Queries Generated due to not using WHERE EXISTS

[Django]

#25789: Inefficient Queries Generated due to not using WHERE EXISTS
-+-
 Reporter:  Alex Rothberg|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by James Howe):

 Similarly, I have a use-case where this query structure has the only
 acceptable performance (in PostgreSQL):
 {{{#!sql
 ... FROM model_1
 WHERE NOT EXISTS (
   SELECT TRUE FROM model_2
   WHERE model_1.pkey = model_2.fkey
 AND (model_2.property IS NULL OR model_2.property >= 42)
 )
 }}}

 Currently using `extra()` to do it.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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.de37d52893e5e1c2b46b51c6527f126f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29678: inspectdb fails on MySQL 8 with " 'utf8' is currently an alias for the character set UTF8MB3" (was: MySQL 8.0.12 manage.py inspectdb fails)

[Django]

#29678: inspectdb fails on MySQL 8 with " 'utf8' is currently an alias for the
character set UTF8MB3"
-+-
 Reporter:  SuilAmhain   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  2.1
  commands)  |   Resolution:
 Severity:  Normal   |  worksforme
 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):

 * type:  Uncategorized => Bug


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

Re: [Django] #29678: MySQL 8.0.12 manage.py inspectdb fails

[Django]

#29678: MySQL 8.0.12 manage.py inspectdb fails
-+-
 Reporter:  SuilAmhain   |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Core (Management |  Version:  2.1
  commands)  |   Resolution:
 Severity:  Normal   |  worksforme
 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:   => worksforme


Comment:

 I can't reproduce the failure with MySQL 8. I see the warning but it's not
 an exception. I guess there might be some code in your environment like
 what was removed in the commit I referenced above. If you're able to debug
 further and find that Django is at fault, please reopen with an
 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 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.5988e6c91069d2861fdadeca52566881%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29678: MySQL 8.0.12 manage.py inspectdb fails

[Django]

#29678: MySQL 8.0.12 manage.py inspectdb fails
-+-
 Reporter:  SuilAmhain   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Core (Management |  Version:  2.1
  commands)  |
 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 SuilAmhain):

 * Attachment "base.py" added.

 Django 2.1 django/db/backends/mysql/base.py

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

Re: [Django] #8961: Add support for sending emails directly through MTA

[Django]

#8961: Add support for sending emails directly through MTA
---+-
 Reporter:  Ivan Giuliani  |Owner:  Ivan Giuliani
 Type:  Uncategorized  |   Status:  closed
Component:  Core (Mail)|  Version:  1.0
 Severity:  Normal |   Resolution:  wontfix
 Keywords:  mail, email| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by pere):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 From https://djangosnippets.org/snippets/1864/ it can be seen that there
 has been code around to do this since at least 2010.  There is already a
 python package available from https://github.com/perenecabuto/django-
 sendmail-backend/ , which is also available from pipy.

 The backend is only 50 lines of code.  It is a pitty it isn't part of the
 default Django distribution, given that /usr/sbin/sendmail is the standard
 way to send email on a unix and linux server.

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

Re: [Django] #29500: SQLite functions crashes on NULL values

[Django]

#29500: SQLite functions crashes on NULL values
-+-
 Reporter:  Sergey Fedoseev  |Owner:  Nick Pope
 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 Nick Pope):

 * owner:  (none) => Nick Pope
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

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

Re: [Django] #29677: StaticFilesStorage.post_process does not seem to exist, contrary to documentation

[Django]

#29677: StaticFilesStorage.post_process does not seem to exist, contrary to
documentation
--+
 Reporter:  Atul Varma|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  2.1
 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:"5628a8a23f462229a6511aa9d7875efae8ae54d5" 5628a8a2]:
 {{{
 #!CommitTicketReference repository=""
 revision="5628a8a23f462229a6511aa9d7875efae8ae54d5"
 [2.1.x] Fixed #29677 -- Doc'd return value of
 StaticFilesStorage.post_process().

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

Re: [Django] #29677: StaticFilesStorage.post_process does not seem to exist, contrary to documentation

[Django]

#29677: StaticFilesStorage.post_process does not seem to exist, contrary to
documentation
--+
 Reporter:  Atul Varma|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  2.1
 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:"7f6b013bf60e6168a7e0a8f2b97954c3a45725e0" 7f6b013b]:
 {{{
 #!CommitTicketReference repository=""
 revision="7f6b013bf60e6168a7e0a8f2b97954c3a45725e0"
 Fixed #29677 -- Doc'd return value of StaticFilesStorage.post_process().
 }}}

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

Re: [Django] #29678: MySQL 8.0.12 manage.py inspectdb fails

[Django]

#29678: MySQL 8.0.12 manage.py inspectdb fails
-+-
 Reporter:  SuilAmhain   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Core (Management |  Version:  2.1
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by SuilAmhain):

 What can I provide as further  evidence?

 I am using a number of MySQL 8 features related to JSON so downgrading to
 a lower version is not viable. I am not explicitly tied to Django, but I
 really wanted to learn it.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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.882031206b169108d7296c9d3e137a0e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29646: Document the validators that each model and form field uses

[Django]

#29646: Document the validators that each model and form field uses
-+-
 Reporter:  Shrey Batra  |Owner:  Jeff
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Accepted => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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.70c9c2baa2e707662f12765437523604%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.