Knex.js Date object serialization across dialect drivers

Knex.js delegates the serialization of JavaScript Date objects to the underlying database driver (such as pg, mysql2, or tedious). Because Knex acts as a query builder rather than an ORM with a built-in abstraction layer for timezones, the resulting database entry depends on the driver's internal handling and the Node.js process environment.

When deploying applications across multiple regions, there is uncertainty regarding how different dialects treat the implicit conversion of a Date object when no explicit timezone is defined in the connection configuration. This creates a risk of inconsistent data storage when switching between PostgreSQL and MySQL, as they handle TIMESTAMP and DATETIME types differently.

• Does Knex.js provide a dialect-agnostic way to ensure consistent UTC serialization of Date objects without relying on the TZ environment variable?
• Which driver-specific configuration settings are recommended to standardize date conversion across different SQL dialects?