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
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists
Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....
Importing the staged config throws an error: another field with the same name already exists