If you configure the session mode to ANSI, then the compare on character based strings will be case sensitive. Teradata is a none case sensitive database but the comparing of strings will take case into consideration when mode is ansi. We don't use the CASESPECIFIC or NOT CASESPECIFIC keywords in our extraction and instead consider teradata as not case sensitive.
We need to adjust the connections isCaseSensitive() return value to take into consideration the TMODE setting. When you right click on the following example and choose the "edit table data" action, the extraction should find the object in ANSI and TERADATA modes.
CREATE MULTISET TABLE <database>zTesT2, NO FALLBACK, NO BEFORE JOURNAL, NO AFTER JOURNAL, CHECKSUM = DEFAULT, DEFAULT MERGEBLOCKRATIO (col2 VARCHAR(25) CHARACTER SET LATIN CASESPECIFIC) PRIMARY INDEX (col2)
|
354 KB
I have made modifications so that when the connection, if the database type is teradata, we query the sessioninfo[V][X] for the transaction_mode. If the transaction mode is ANSI we will consider the database to be in case sensitive mode.
Committed revision: 52883, 52884
Verified in ADS-18.0.0-Preview-48 and ADS-17.0.11-7
1. Connect to Teradata database
2. Right click on server and select Server properties,Now set parameter value under Driver tab
TMODE=ANSI
3. Open QA window and execute below script.
CREATE MULTISET TABLE Test_raghavzTesT2, NO FALLBACK, NO BEFORE JOURNAL, NO AFTER JOURNAL, CHECKSUM = DEFAULT, DEFAULT MERGEBLOCKRATIO (col2 VARCHAR(25) CHARACTER SET LATIN CASESPECIFIC) PRIMARY INDEX (col2)
4. Right click on created table and select Edit Table Data option.
Verified in ADS-18.0.0-Preview-48 and ADS-17.0.11-7
1. Connect to Teradata database
2. Right click on server and select Server properties,Now set parameter value under Driver tab
TMODE=ANSI
3. Open QA window and execute below script.
CREATE MULTISET TABLE Test_raghavzTesT2, NO FALLBACK, NO BEFORE JOURNAL, NO AFTER JOURNAL, CHECKSUM = DEFAULT, DEFAULT MERGEBLOCKRATIO (col2 VARCHAR(25) CHARACTER SET LATIN CASESPECIFIC) PRIMARY INDEX (col2)
4. Right click on created table and select Edit Table Data option.
Issue #14971 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build v17.0.11-7, v18.0.0-preview-45 |
No time estimate |
I have made modifications so that when the connection, if the database type is teradata, we query the sessioninfo[V][X] for the transaction_mode. If the transaction mode is ANSI we will consider the database to be in case sensitive mode.
Committed revision: 52883, 52884