Supertask for cleaning up temporal (date/time-related) handling in server
Things that need to be refactored and cleaned up regarding temporal values in the server:
1) Removal of timezones from the main server
2) Document and clean up the routines for calculating day numbers, weeks, weekdays, etc.
3) Create an object-oriented way to deal with temporal values (date, datetime, time, timestamp, microtimestamp, nanotimestamp)
4) Remove zero and fuzzy-date warnings and turn them into errors
5) Remove the localXXX() functions
6) Create a new CURRENT_TIMESTAMP() function and make NOW() a synonym for it.
7) Create separate and full test cases which test the edge cases for date/time handling
8) Streamline the way temporal values are handled by reducing the conversion operations in the Item and Field hierarchy as much as possible.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- High
- Drafter:
- Jay Pipes
- Direction:
- Needs approval
- Assignee:
- Jay Pipes
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
-
cirrus
- Started by
- Jay Pipes
- Completed by
- Lee Bieber
Related branches
Related bugs
Sprints
Whiteboard
50% DONE --> 1) Removal of timezones from the main server
COMPLETED --> 2) Document and clean up the routines for calculating day numbers, weeks, weekdays, etc.
COMPLETED --> 3) Create an object-oriented way to deal with temporal values (date, datetime, time, timestamp, microtimestamp, nanotimestamp)
90% DONE --> 4) Remove zero and fuzzy-date warnings and turn them into errors
5) Remove the localXXX() functions
6) Create a new CURRENT_TIMESTAMP() function and make NOW() a synonym for it.
50% DONE --> 7) Create separate and full test cases which test the edge cases for date/time handling
50% DONE --> 8) Streamline the way temporal values are handled by reducing the conversion operations in the Item and Field hierarchy as much as possible.
