ADS Version: 14.0.0-beta-76
Operating Environment:Windows 8 64 bit.
Database: Teradata Aster Database.
Connect to Aster database, expand database node, now by default you will have two schema names, "public" and "nc_system" .Now open a Query Analyzer window and look for schema name, over there schema name will be " beehive". So either under database schema "beehive " is not getting populated or Query Analyzer window is showing wrong schema name.
|
57 KB
This is as designed but will look into seen if they have added a way to extract the current schema. I see they have the SHOW SEARCH_PATH; SET SEARCH_PATH = SearchPathString; commands but they are not working correctly for me
Rohit, can you verify in 14.0.0-rc-2 ?
What you have logged is a known issue. Below are the 2 things to note:
1. In earlier versions, we were displaying the database in Schema: You will no longer see the database name like beehive in 14.0.0-rc-2 ?
2. In the tree node, if you click on nc_system and then open a query window, it will still display the Schema as public, because executing the 2 queries below:
set search_path='nc_system'
go
show search_path
go
Rohit, can you verify in 14.0.0-rc-2 ?
What you have logged is a known issue. Below are the 2 things to note:
1. In earlier versions, we were displaying the database in Schema: You will no longer see the database name like beehive in 14.0.0-rc-2 ?
2. In the tree node, if you click on nc_system and then open a query window, it will still display the Schema as public, because executing the 2 queries below:
set search_path='nc_system'
go
show search_path
go
Issue #9728 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build v14.0.0-rc-2 |
No time estimate |
1 issue link |
relates to #9792
Issue #9792In fluidhsell sqldump command not working for aster database |
This is as designed but will look into seen if they have added a way to extract the current schema. I see they have the SHOW SEARCH_PATH; SET SEARCH_PATH = SearchPathString; commands but they are not working correctly for me