Hi Mario,

After further investigation I found that we intentionally use a static string output because zone information is just not available from Snowflake in a jdbc timestamp object. Depending on the format from the server,  converting a timestamp_tz column as a string will yield the complete timestamp. If we try to stick the retrieved information into a java timestamp object, it will not show the zone information correctly. 

We should not allow a user to modify the result format in options for the timestamp data types.  This should change if we continue to use string as a option.

I will leave this issue open to investigate further for a future release.

Thanks,

Tom

Hi Tom,

Do I need to hide the TimeStamp datatype variations in snowflake here also??

I am attaching the screenshot for the same.

Thanks

<asif>

NO; we need these timestamp datatypes here.

<asif>

Fixed in SVN Revision: 58939

Removed the Timestamp datatype and its variations in Results Format

>>SVN Revision: 58939

We should remove the list addition code instead of commenting out.

Asif

Agreed

>> We should remove the list addition code instead of commenting out.

Fixed in SVN Revision: 58949

Removed the Timestamp datatype and its variations in Results Format

QA Verified issue: Results format timestamp option doesn't change the format on Snowflake

and its working fine and as expected

OS - Windows 8.1, Ubuntu, Mac

Build - dev-13-no-ofsc/

Test Rail link :

Windows: ADS 22.1 Test Suite (Windows) - TestRail

MAC: ADS 22.1 Test Suite (MAC) - TestRail

Ubuntu: ADS 22.1 Test Suite(Ubuntu) - TestRail

Thanks,

Shubham Tripathi

I will reopen this issue to investigate if the timestamp issue with the jdbc got fixed. If it did, we should be able to turn the formatting back on.