#32699: Comparisons using TruncTime are unreliable in MySQL
-------------------------------+------------------------------------
Reporter: Alex Hill | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 3.2
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 Alex Hill):
I appreciate the insight, thanks! Good to hear it shouldn't be more
complicated than the existing patch.
> Which is kind of expected as TIME returns a string representation of the
temporal value
All representations of the same time passed to TIME seem to be considered
equal to one another when compared, even though the strings they evaluate
to may not equal to one another. Can you shed any light?
{{{
mysql> SELECT TIME('10:30:000000') = TIME('10:30');
1
mysql> SELECT TIME('10:30:00.000000'), TIME('10:30');
10:30:00.000000 10:30:00
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32699#comment:2>
Django <https://code.djangoproject.com/>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.9f420f6f7c6e01e880ae7f6f24bce9fe%40djangoproject.com.
