Re: [Django] #33037: TruncDay error when using offset timezones on MySQL, SQLite, and Oracle.

2024-02-15 Thread Django
#33037: TruncDay error when using offset timezones on MySQL, SQLite, and Oracle.
-+-
 Reporter:  Alan |Owner:  Shafiya
 |  Adzhani
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  mysql truncdate  | Triage Stage:  Ready for
  timezone   |  checkin
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:"22285d366c9061a668003638613685f5a135a4c3" 22285d3]:
 {{{#!CommitTicketReference repository=""
 revision="22285d366c9061a668003638613685f5a135a4c3"
 Fixed #33037 -- Fixed Trunc() with offset timezones on MySQL, SQLite,
 Oracle.
 }}}
-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018dac409287-b50a09b5-f4f5-434b-898a-e0616910702e-00%40eu-central-1.amazonses.com.


Re: [Django] #33037: TruncDay error when using offset timezones on MySQL, SQLite, and Oracle.

2024-02-15 Thread Django
#33037: TruncDay error when using offset timezones on MySQL, SQLite, and Oracle.
-+-
 Reporter:  Alan |Owner:  Shafiya
 |  Adzhani
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql truncdate  | Triage Stage:  Ready for
  timezone   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018dac043bb7-0b13b1bf-00c6-4889-8d1f-0b2ffccd5575-00%40eu-central-1.amazonses.com.


Re: [Django] #33037: TruncDay error when using offset timezones on MySQL, SQLite, and Oracle.

2024-02-03 Thread Django
#33037: TruncDay error when using offset timezones on MySQL, SQLite, and Oracle.
-+-
 Reporter:  Alan |Owner:  Shafiya
 |  Adzhani
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql truncdate  | Triage Stage:  Accepted
  timezone   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Shafiya Adzhani):

 * has_patch:  0 => 1

Comment:

 Added patch here: https://github.com/django/django/pull/17814
-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d6f25fc1d-dfd6078b-84ff-48e4-8f90-6b748f7b64a6-00%40eu-central-1.amazonses.com.


Re: [Django] #33037: TruncDay error when using offset timezones on MySQL, SQLite, and Oracle.

2024-01-25 Thread Django
#33037: TruncDay error when using offset timezones on MySQL, SQLite, and Oracle.
-+-
 Reporter:  Alan |Owner:  Shafiya
 |  Adzhani
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql truncdate  | Triage Stage:  Accepted
  timezone   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Shafiya Adzhani):

 * owner:  nobody => Shafiya Adzhani
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d443cf115-d86f2c5d-1207-4a62-a8e1-61990798e59e-00%40eu-central-1.amazonses.com.


Re: [Django] #33037: TruncDay error when using offset timezones on MySQL, SQLite, and Oracle.

2024-01-25 Thread Django
#33037: TruncDay error when using offset timezones on MySQL, SQLite, and Oracle.
-+-
 Reporter:  Alan |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql truncdate  | Triage Stage:  Accepted
  timezone   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Shafiya Adzhani):

 This ticket is still open, right? I will try to understand it and create
 the patch.
-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018d443be87f-ad3b79ec-9055-46c8-b12b-98982274d914-00%40eu-central-1.amazonses.com.


Re: [Django] #33037: TruncDay error when using offset timezones on MySQL, SQLite, and Oracle.

2023-01-09 Thread Django
#33037: TruncDay error when using offset timezones on MySQL, SQLite, and Oracle.
-+-
 Reporter:  Alan |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql truncdate  | Triage Stage:  Accepted
  timezone   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Kenneth Lim):

 Strictly speaking, would this be better handled by modifying the name
 handling instead? Here we'll convert directly from etc/GMT+9 -> "-9:00",
 rather than passing "etc/GMT+9" directly over to mysql

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701859ab04228-3a30e208-4c88-4902-aef6-c061d3391c75-00%40eu-central-1.amazonses.com.


Re: [Django] #33037: TruncDay error when using offset timezones on MySQL, SQLite, and Oracle. (was: TruncDay error when using offset timezones on MySQL)

2021-08-25 Thread Django
#33037: TruncDay error when using offset timezones on MySQL, SQLite, and Oracle.
-+-
 Reporter:  Alan |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  mysql truncdate  | Triage Stage:  Accepted
  timezone   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 > This fix the issue. Maybe the same problem is also happening with
 Oracle, at least the code in _prepare_tzname_delta is the same as the
 MySQL.

 Slice in `_prepare_tzname_delta()` is not important because `tzname` will
 be `-03` after fixing #32992. I reproduced the same issue on Oracle and
 SQLite.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.bcc14379870d4fabf1fdee58b357e25c%40djangoproject.com.