The SQL used to manage dates and times varies by database type. The code to generate this SQL (e.g., DATE_FORMAT() or FROM_UNIXTIME()) has historically been handled by modules that work with dates and times, wrapped in long switch statements to handle the officially supported databases. (more or less.) A d.o issue raised the possibility of a date abstraction API, but nothing ever came of it.
Similar to #2888, this is code that was created to support PostgreSQL in Silkscreen and is submitted here because the non-PostgreSQL part of the patch is valid for Backdrop, even if all it accomplishes is better encapsulation of database code in the database classes.
Unlike #2888 and #2889, this is a little more invasive, changing the date_sql_handler class in the Date module, and several Views handlers.
As with #2888, I'm submitting this because I consider it good open source etiquette to provide patches to parent projects, even if the patch's true purpose cannot be realized upstream, in this case database independence.
Recent comments
Hi folks, I went ahead and ported all drush 8.x stuff to PHP 8.3 and completely ripped out the legacy Symfony 2 internals. You can check out the exact details of what was done in the PR...
Using Drush 8 with php 8
The inability to check for and install updates makes website development and maintenance extremely difficult. Managing over ten websites across two different hosting providers—one of which is...
Unable to run update - fails with Connection timed out
Thanks for the response, Herb! Since I posted that I did some more testing and have posted this issue https://github.com/backdrop-contrib/tfa_basic/issues/33 In fact, if both email...
TFA - how to setup fallback options 'per user'