↧
Difference between ANSI and TERA modes with respect to record insertion - response (2) by tomnolan
↧
Channel:
Teradata Forums - Database
X
Are you the publisher?
Claim or
contact us
about this channel.
X
0
Channel Details:
- Title: Teradata Forums - Database
- Channel Number: 4412770
- Language: English
- Registered On: September 11, 2012, 5:26 pm
- Number of Articles: 14773
- Latest Snapshot: September 8, 2016, 12:38 am
- RSS URL: http://forums.teradata.com/forum/database/rss.xml
- Publisher: /forum/database
- Description: Database Forum topics and responses
- Catalog: //teradata197.rssing.com/catalog.php?indx=4412770
© 2025 //www.rssing.com
soumyajit, you were misinformed. The Teradata Database never "ignores" duplicate records when doing inserts, no matter which transaction mode (ANSI vs TERA) you are using.
As Carlos said, the table attribute (SET vs MULTISET) governs whether duplicate rows are permitted in a table. With a MULTISET table, you are permitted to insert duplicate rows using either ANSI or TERA mode.
In contrast, with a SET table, if you try to insert duplicate rows, you will get Teradata Database error 2802 "Duplicate row error in <table>" using either ANSI or TERA mode. In other words, the transaction mode does not change this behavior.