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
|
|
73 KB
When we create Synonym using "View" then it occurs in tree node.
There seems to be issues with the SYNONYMS catalog view. We can re-write the tree node to use the OBJECTS table to get the synonym names. This will cause us to lose the is_valid information on the synonym objects. The extraction requires using the SYNONYM catalog view for information that is not available in the objects views, but will work fine when extracting information for individual synonyms.
There is still in issue on how to do mass synonym info extraction as this will cause there catalog view to throw a sql exception. This can be experiences in data studio via schema script generator. Also this does not happen until there is data in the catalog tables that cause it. Not sure what the combination of data is yet...
There seems to be issues with the SYNONYMS catalog view. We can re-write the tree node to use the OBJECTS table to get the synonym names. This will cause us to lose the is_valid information on the synonym objects. The extraction requires using the SYNONYM catalog view for information that is not available in the objects views, but will work fine when extracting information for individual synonyms.
There is still in issue on how to do mass synonym info extraction as this will cause there catalog view to throw a sql exception. This can be experiences in data studio via schema script generator. Also this does not happen until there is data in the catalog tables that cause it. Not sure what the combination of data is yet...
it appears that the more data in the tables the less the catalog table SYNONYMS is working. Not sure how to work around this just yet...
it appears that the more data in the tables the less the catalog table SYNONYMS is working. Not sure how to work around this just yet...
Came up with extra irrelevant WHERE clause conditions that will allow for there view source to not throw the multi row exception that will not affect the condition of the objects we wish to extract. Issue fixed. Will continue to use the Synonym catalog view over the Objects view so we can extract all the needed information.
Came up with extra irrelevant WHERE clause conditions that will allow for there view source to not throw the multi row exception that will not affect the condition of the objects we wish to extract. Issue fixed. Will continue to use the Synonym catalog view over the Objects view so we can extract all the needed information.
Issue #13578 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build v17.0.0-dev-90 |
| No time estimate |
When we create Synonym using "View" then it occurs in tree node.