5. Composite Index Statement is wrong in Teradata.
Actual Statement:
create index NameIndex on tablename(col1, col2) ;
Expected Statement:
create index NameIndex (col1, col2) on tablename;
Please help me to solve this issue in teradata.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
hi,
1. HBM2DDL=UPDATE => Only new tables are getting created; ALTER statements are not getting generated for TERADATA.
2. Composite Primary Key => Column Name is not having the attributeoverrides column name in In Teradata.
3. Fk Reference and Self Reference => Duplicate Table is getting generated for the references. <TableName>_0 in Teradata.
4. Composite Unique/Unique constraint => new table is getting created which is not required from client side. how to avoid this.
create table hibernate_unique_key (
next_hi INTEGER
);
insert into hibernate_unique_key values ( 0 );
5. Composite Index Statement is wrong in Teradata.
Actual Statement:
create index NameIndex on tablename(col1, col2) ;
Expected Statement:
create index NameIndex (col1, col2) on tablename;
Please help me to solve this issue in teradata.