Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Low |
| Complexity | Unknown |
| Component | App - Visual Editing |
| Version | 16.0 |
|
|
146 KB
Do you get an error message ?
Does it happen for names < 30?
Does it happen in Teradata v14.1 and below ?
Do you get an error message ?
->I am not getting any error message on Drop trigger option
Does it happen for names < 30?
->Working fine when we use <30 character.
Does it happen in Teradata v14.1 and below ?
->"Give error message "Name requires more than 30 bytes in LATIN internal form.",on creating trigger using 31 character.
Do you get an error message ?
->I am not getting any error message on Drop trigger option
Does it happen for names < 30?
->Working fine when we use <30 character.
Does it happen in Teradata v14.1 and below ?
->"Give error message "Name requires more than 30 bytes in LATIN internal form.",on creating trigger using 31 character.
There are multiple issues that needed to be fixed here. First is that [X] tables where not be used and those [V] tables where not getting set as the code is working together. Next is triggers need to have the <db_name>.<trigger_name> scripted. If your connection was in database A yet you attempt to drop a trigger in database Y without specifying the database the trigger will not be found. At least this is the case for triggers with greater then 30 characters. This has impact on the GUI.
Scripting will script the database name in the ddl now and Triggers will drop now from the tree.
There are multiple issues that needed to be fixed here. First is that [X] tables where not be used and those [V] tables where not getting set as the code is working together. Next is triggers need to have the <db_name>.<trigger_name> scripted. If your connection was in database A yet you attempt to drop a trigger in database Y without specifying the database the trigger will not be found. At least this is the case for triggers with greater then 30 characters. This has impact on the GUI.
Scripting will script the database name in the ddl now and Triggers will drop now from the tree.
fixes made so that trigger name is qualified with the database name to insure sql scripts will find the trigger correctly.
fixes made so that trigger name is qualified with the database name to insure sql scripts will find the trigger correctly.
Issue #13297 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build v16.0.5-6 |
| No time estimate |
1 issue link |
relates to #13288
Issue #13288Teradata -> 14.10 and above -> Need to migrate extraction to use V views in order |
Do you get an error message ?
Does it happen for names < 30?
Does it happen in Teradata v14.1 and below ?