[Django] #33075: '__date' returns None in MySQL while it returns date object in Sqlite3

9 views
Skip to first unread message

Django

unread,
Aug 31, 2021, 12:27:25 PM8/31/21
to django-...@googlegroups.com
#33075: '__date' returns None in MySQL while it returns date object in Sqlite3
-----------------------------------------+------------------------
Reporter: muhanpixie | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 3.2
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 |
-----------------------------------------+------------------------
database: mysql 5.7
django version: 3.2
python version: 3.8.1


{{{Model.objects.values('some_datetime_field__date',) }}} returns None in
MYSQL

{{{
class Inbound(models.Model):
effective_date = models.DateTimeField(null=False, blank=True)
number = models.IntegerField()
# other fields.

daily_changes = Inbound.objects.all().values('effective_date__date')\
.annotate(total_change=Sum('number')).
Inbound.objects.values('effective_date__date')
}}}


just returns Nones in Mysql

--
Ticket URL: <https://code.djangoproject.com/ticket/33075>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Aug 31, 2021, 12:28:53 PM8/31/21
to django-...@googlegroups.com
#33075: '__date' returns None in MySQL while it returns date object in Sqlite3
-------------------------------+--------------------------------------

Reporter: muhanpixie | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 3.2
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
-------------------------------+--------------------------------------
Description changed by muhanpixie:

Old description:

> database: mysql 5.7
> django version: 3.2
> python version: 3.8.1
>

> {{{Model.objects.values('some_datetime_field__date',) }}} returns None in
> MYSQL
>

>
> {{{
> class Inbound(models.Model):
> effective_date = models.DateTimeField(null=False, blank=True)
> number = models.IntegerField()
> # other fields.
>
> daily_changes = Inbound.objects.all().values('effective_date__date')\
> .annotate(total_change=Sum('number')).
> Inbound.objects.values('effective_date__date')
> }}}
>

>

> just returns Nones in Mysql

New description:

database: mysql 5.7
django version: 3.2
python version: 3.8.1


{{{Model.objects.values('some_datetime_field__date',) }}} returns None in
MYSQL

{{{
class Inbound(models.Model):
effective_date = models.DateTimeField(null=False, blank=True)
number = models.IntegerField()
# other fields.

daily_changes = Inbound.objects.all().values('effective_date__date')\
.annotate(total_change=Sum('number')).
Inbound.objects.values('effective_date__date')
}}}


The code just returns Nones in Mysql. But it returns date object with
Sqlite

--

--
Ticket URL: <https://code.djangoproject.com/ticket/33075#comment:1>

Django

unread,
Aug 31, 2021, 1:49:17 PM8/31/21
to django-...@googlegroups.com
#33075: '__date' returns None in MySQL while it returns date object in Sqlite3
-------------------------------------+-------------------------------------
Reporter: pikicode | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: mysql | Triage Stage:

| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):

* keywords: => mysql
* resolution: => invalid
* status: new => closed
* component: Uncategorized => Database layer (models, ORM)


Comment:

When `USE_TZ` is `True`, fields are converted to the current time zone
before filtering (see
[https://docs.djangoproject.com/en/3.2/ref/models/querysets/#date __date
docs]). This requires
[https://docs.djangoproject.com/en/3.2/ref/models/querysets/#database-
time-zone-definitions time zone definitions in the database]. Please check
that `mysql_tzinfo_to_sql` is loaded to the time zone tables.

--
Ticket URL: <https://code.djangoproject.com/ticket/33075#comment:2>

Reply all
Reply to author
Forward
0 new messages