KB-2127 CONVERT_TZ() function returns null in phpMyAdmin

Parmida Borhani — Wed, 03 Jun 2020 03:27:55 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 6/3/2020 3:27:55 AM

Symptoms

On Appian Cloud environments, the CONVERT_TZ() function returns NULL in phpMyAdmin when using timezone names, such as SELECT CONVERT_TZ(NOW(),'US/Eastern','Europe/Paris');.

Cause

Appian Cloud environments do not support populating the MySQL timezone tables for the MySQL database included in the Cloud environment.

A product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.

Action

If you would like to use this functionality and would like to be added to the existing product use case (#1391 - Populate time zone tables in Appian Cloud MySQL database), please open a support case with Appian. Meanwhile, Appian Support strongly recommends that you transition to the following approach as a best practice:

Date and time values stored in the database should always be in GMT/UTC. Any conversion to a user's local timezone should be handled in the presentation layer (i.e., in Appian SAIL interfaces). If you have a use case to convert a user input, one approach is to use an online API to convert the timezone. For example, Google has the following API.

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: June 2020

Tags: phpmyadmin, database, mysql, product use cases, Cloud, open use cases

KB-2127 CONVERT_TZ() function returns null in phpMyAdmin

Parmida Borhani — Wed, 03 Jun 2020 03:27:39 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 6/3/2020 3:27:39 AM

Symptoms

On Appian Cloud environments, the CONVERT_TZ() function returns NULL in phpMyAdmin when using timezone names, such as SELECT CONVERT_TZ(NOW(),'US/Eastern','Europe/Paris');.

Cause

Appian Cloud environments do not support populating the MySQL timezone tables for the MySQL database included in the Cloud environment.

Action

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: June 2020

Tags: phpmyadmin, mysql, product use cases, Cloud, open use cases

DRAFT SP-4480 CONVERT_TZ() function returns null in phpMyAdmin

Tom Ryan — Tue, 02 Jun 2020 08:27:58 GMT

Revision 3 posted to Appian Knowledge Base by Tom Ryan on 6/2/2020 8:27:58 AM

Symptoms

On Appian Cloud environments, the CONVERT_TZ() function returns NULL in phpMyAdmin when using timezone names, such as SELECT CONVERT_TZ(NOW(),'US/Eastern','Europe/Paris');.

Cause

Appian Cloud environments do not support populating the MySQL timezone tables for the MySQL database included in the Cloud environment.

Action

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: June 2020

Tags: known issues, mysql, Cloud, open issues, open use cases

DRAFT SP-4480 CONVERT_TZ() function returns null in phpMyAdmin

Tom Ryan — Tue, 02 Jun 2020 08:26:31 GMT

Revision 2 posted to Appian Knowledge Base by Tom Ryan on 6/2/2020 8:26:31 AM

Symptoms

On Appian Cloud environments, the CONVERT_TZ() function returns NULL in phpMyAdmin when using timezone names, such as SELECT CONVERT_TZ(NOW(),'US/Eastern','Europe/Paris');.

Cause

Appian Cloud environments do not support populating the MySQL timezone tables for the MySQL database included in the Cloud environment.

Action

Date/time values stored in the database should always be in GMT/UTC. Any conversion to the local timezone should be handled in the presentation layer (our UI layer already handles converting data/time values to the local timezone). If you have a use case to convert a user input, one approach is to use an online API to convert the timezone. For example, Google has the following API.

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: June 2020

Tags: known issues, mysql, Cloud, open issues, open use cases

DRAFT SP-4480 CONVERT_TZ() function returns null in phpMyAdmin

Nicholas Van Dyke — Mon, 01 Jun 2020 19:47:58 GMT

Revision 1 posted to Appian Knowledge Base by Nicholas Van Dyke on 6/1/2020 7:47:58 PM

Symptoms

The CONVERT_TZ() function returns NULL in phpMyAdmin when using timezone names, such as SELECT CONVERT_TZ(NOW(),'US/Eastern','Europe/Paris');.

Cause

The MySQL timezone tables have not been populated, as described in the documentation.

This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.

Action

If you are facing this issue and would like to be added to the existing product use case (#1391 - Populate time zone tables in Appian Cloud MySQL database), please open a support case with Appian. Meanwhile, Appian Support strongly recommends that you transition to the following approach as a best practice:

Date/time values stored in the database should always be in GMT/UTC. Any conversion to the local timezone should be handled in the presentation layer (our UI layer already handles converting data/time values to the local timezone). If you have a use case to convert a user input, you should consider using a web API (these will be current). For example, Google has the following API.

Affected Versions

This article applies to all versions of Appian Cloud.

Last Reviewed: June 2020

Tags: known issues, mysql, Cloud, open issues, open use cases