Fix back-end not supporting time zones

[benanhalt]

https://docs.djangoproject.com/en/3.0/ref/settings/#std:setting-TIME_ZONE

https://docs.djangoproject.com/en/3.0/topics/i18n/timezones/

[maxpatiiuk]

This affects the front-end. More info:

specify7/specifyweb/frontend/js_src/lib/components/internationalization.tsx

Lines 177 to 188 in 4d007df

	if (timePassed < 0) {
	/*
	* This happens due to time zone conversion issues.
	* Need to fix that issue on the back-end first.
	* See: https://github.com/specify/specify7/issues/641
	* Adding support for future dates is not hard, but it would be weird to
	* create a data set and see its date of creation be 5 hours into the
	* future
	*/
	// Throw new Error('Future dates are not supported');
	console.error('Future dates are not supported');
	return relativeDate.format(0, 'second');

[maxpatiiuk]

From @chanulee1:

The "Date Edited" field on the CO form is populated with tomorrow's date. Current date at time of writing this issue: 8:37 pm 11/24/2022 CST.

nBbv7u4Kdx.mp4

https://freshfish-edge.test.specifysystems.org/specify/view/collectionobject/new/

[maxpatiiuk]

@melton-jason I know you looked into this issue. If you faced a roadblock preventing you from fixing this issue, please post the details here for future reference

[melton-jason]

Yes, I did run into a roadblock when testing my fix.
The fix involves enabling the setting which allows Django to be time-zone aware. With this setting enabled however, it now no longer supports naive datetime objects, and throws an error if one is encountered.
More specifically, Django expects every date object to have a tzinfo (timezone info) attribute.

Fields like Timestamp Created and Timestamp modified work correctly, but entering a date through the Partial Date field (like cataloged date on CollectionObject) and saving a record will always throw an error.

Solutions

The best-case solution for this would be to create a middleware which catches any naive datetime objects and converts them to aware datetime objects.

Otherwise, we would have to go through the backend and make sure every datetime object is aware anywhere the backend could expect a date/time object.

In both of these solutions, we would have to assume some timezone information (most likely midnight).