I would like to know if the precision can be included when scripting tables? For example, include the "(0)" as seen below; currently, it does not include the precision as highlighted below (I added it manually for this example).
We are using Teradata 16.20 (not Aster).
Support info:
Product: Aqua Data Studio
Version: 20.6.1-1
Build #: 57822
Build Date: 2020-Jul-16 02:59:36 PM
Operating Environment: Windows 10 (10.0, amd64) / Cp1252 / en / US / AdoptOpenJDK 1.8.0_222-b10
Memory: Max=1,908,932,608; Total=1,632,108,544; Free=377,076,320; CPUs=6
In-Window Graphics Capabilities
Graphics Vendor: Microsoft Corporation
OpenGL Renderer: GDI Generic
OpenGL Version: 1.1.0
Double-Buffering: Disabled
Anti-Aliasing: Disabled
Anti-Aliasing Sample Count: 0
Hardware Acceleration: Disabled
Color Bits: Red: 8 Green: 8 Blue: 8 Alpha: 0
Depth Bits: 16
Accumulation Buffer Bits: Red: 16 Green: 16 Blue: 16
Initialization Time: 1952 ms
Offscreen Graphics Capabilities
Graphics Vendor: Brian Paul
OpenGL Renderer: Mesa OffScreen
OpenGL Version: 2.1 Mesa 7.8.2
Double-Buffering: Disabled
Anti-Aliasing: Disabled
Anti-Aliasing Sample Count: 0
Hardware Acceleration: Disabled
Color Bits: Red: 8 Green: 8 Blue: 8 Alpha: 8
Depth Bits: 16
Accumulation Buffer Bits: Red: 16 Green: 16 Blue: 16
Initialization Time: 95 ms
Hardware PBuffer Available: No
Using PBuffer: No
Using Ram Buffer: Yes
Offscreen Rendering: Enabled
Offscreen Buffer Size: 800x600
17 KB
792 B
57 KB
177 KB
210 KB
68 KB
91 KB
I attached a patch to fix this. It should be tested with Teradata 15, 16 and 17.5 for both time and timestamp data types. There is a difference between timestamp(0) and timestamp data types. The latter converts to the default of timestamp(6) ->char(26). The former converts to timestamp->char(19). Please check the Teradata documentation for samples.
Make sure that the data types are displayed correctly in the tree and well as scripting and schema generator.
Hi Nitin,
timestamp(6) = timestamp
timestamp(0) != timestamp
Given this scenario... I created a table at the top with three different timestamp formats. Actually, column c1 and c3 are equal. I did a script object to from the tree to the QA window. The red box shows the create incorrectly. The blue, after I added the patch, shows the create correctly. As you can see the tree is also displaying the columns incorrectly. Make sure that the data types are displayed correctly in the tree and well as scripting and schema generator.
Here is some documentation explaining the differences.
Hope that helps,
Tom
Hi Nitin,
timestamp(6) = timestamp
timestamp(0) != timestamp
Given this scenario... I created a table at the top with three different timestamp formats. Actually, column c1 and c3 are equal. I did a script object to from the tree to the QA window. The red box shows the create incorrectly. The blue, after I added the patch, shows the create correctly. As you can see the tree is also displaying the columns incorrectly. Make sure that the data types are displayed correctly in the tree and well as scripting and schema generator.
Here is some documentation explaining the differences.
Hope that helps,
Tom
Hi Tom
After applying the patch I did the analysis timestamp(0) and timestamp are displayed correctly in the tree and well as scripting and schema generator . I have attached the analysis document above with patch and without patch applying . Please have a look and let me know if there is any scenario is missing or we are good with that
Thanks
Hi Tom
After applying the patch I did the analysis timestamp(0) and timestamp are displayed correctly in the tree and well as scripting and schema generator . I have attached the analysis document above with patch and without patch applying . Please have a look and let me know if there is any scenario is missing or we are good with that
Thanks
Committed in SVN in Revision 58952
After applying the patch Timestamp data types is working fine
Committed in SVN in Revision 58952
After applying the patch Timestamp data types is working fine
Please resolve this issue when done doing unit test.
Please resolve this issue when done doing unit test.
Hi Tom/Asif,
When we are creating table from Create table option then in that case we are getting precision for Time and Timestamp as 6.
Is it expected?
Attaching the screenshot 1 2 here.
With Query analyzer its working fine.
Thanks,
Shubham Tripathi
Hi Tom/Asif,
When we are creating table from Create table option then in that case we are getting precision for Time and Timestamp as 6.
Is it expected?
Attaching the screenshot 1 2 here.
With Query analyzer its working fine.
Thanks,
Shubham Tripathi
Hi Shubham,
Timestamp without the scale set is equivalent to timestamp(6)
Thanks,
Tom
Hi Shubham,
Timestamp without the scale set is equivalent to timestamp(6)
Thanks,
Tom
Issue #15861 |
Verified |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build Dev Build 15 |
No time estimate |
I attached a patch to fix this. It should be tested with Teradata 15, 16 and 17.5 for both time and timestamp data types. There is a difference between timestamp(0) and timestamp data types. The latter converts to the default of timestamp(6) ->char(26). The former converts to timestamp->char(19). Please check the Teradata documentation for samples.
Make sure that the data types are displayed correctly in the tree and well as scripting and schema generator.