Timezone config not being respected.

[belizariogr]

Using the mariadb connector, if i query:

SELECT NOW();

It will be returning the time with timezone from the system. Even though I explicit set the timezone to UTC.

import mariadb from 'mariadb';
import Config from '../../config.js';

const connectionOptions ={
            host: Config.databaseHost || '127.0.0.1',
            port: Config.databasePort || '3306',
            user: Config.databaseUser || 'root',
            password: Config.databasePass || '',
            database: Config.databaseName,
            //dateStrings: true,
            connectionLimit: Config.databaseConnectionLimit || 250,
            multipleStatements: true,
            insertIdAsNumber: true,
            bigIntAsNumber: true,
            decimalAsNumber: true,
            timezone: 'Z'
        };
const pool = mariadb.createPool(connectionOptions);

Using the old mysql connector, everything works fine.

[rusher]

This is tested either using a single connection or pool. Testing it, this works ok.
Could you tell the version of the connector you use?

[belizariogr]

Im using 3.4.0. Just to let you know... Im testing on Windows, with system timezone = -03:00 and MariaDB 11.3, and mariadb timezone set to SYSTEM.

On the old connector... If I change the timezone on the connector config, and query, the result Date will be returned in the timezone specified. Using mariadb connector, it will always return the same result.

Its suposed to return like the example down below:

Example:

Timezone = Z (UTC)
Stored = 2024-11-5T00:00:00
Returned = 2024-11-5T00:00:00

Timezone = -03:00
Stored = 2024-11-5T00:00:00
Returned = 2024-11-4T21:00:00

[Orel-A]

I suspect you are using the toISOString() function.
With this function the date will always print with UTC timezone.
Also check the output of getTimezoneOffset() function

[belizariogr]

There is no point in set timezone on the connection if it will always return the same value. As I said before, using the old connection it works as it should.

[Orel-A]

Check with mysql2 instead. What you get?

[belizariogr]

The real problem is... I have 2 servers: One in Brazil and another one in US. The US server is configured to UTC timezone at system level and the braziliam one -3:00. Im trying to replicate data between those two servers.

The problem is.. When i retrive the date fields on the US server, it will give me using UTC timezone. When I try to retrive the same record on the braziliam server, the backends gets a different result.

Using the old connector, I can get the same result on both servers... Using the mariadb connector, I got different results.

[belizariogr]

Wich means that the timezone option on the connector is doing nothing.

[Orel-A]

Do you have access to PhpMyAdmin to see how the dates are stored?

[belizariogr]

Yes... as I said before.. the dates are the same on both servers.. The problem is not how it is stored. If you change the timezone to another one like +12:00, the result still the same.

[belizariogr]

Just tested... using mysql2... works like charm. Also, using the old mysql works as well.

[Orel-A]

The timezone isn't documented that well: https://github.com/mariadb-corporation/mariadb-connector-nodejs/blob/master/documentation/promise-api.md#timezone-consideration
Maybe try to set timezone to Etc/UTC
Or use skipSetTimezone: true

[belizariogr]

Just tested ans same results using :

skipSetTimezone: true

Just to clarify:

Running the code with System Timezone (-03:00) and Connector Timezone ("Z"):

SELECT NOW();

mysql: 2024-11-14T16:27:13.000Z
mysql2: 2024-11-14T16:27:13.000Z
mariadb: 2024-11-14T19:27:13.000Z

System Timezone (-03:00) and Connector Timezone ("+06:00"):

mysql: 2024-11-14T10:35:09.000Z
mysql2: 2024-11-14T10:35:37.000Z
mariadb: 2024-11-15T01:36:19.000Z

[Orel-A]

The Node.JS application and the Database service are running on the same server?
Also try the Etc/UTC

[belizariogr]

Yes, they are running in the same server.

[Orel-A]

@rusher do you have any idea?