Archives of the TeradataForum
Message Posted: Thu, 26 Aug 2004 @ 13:26:30 GMT
| Subj: | | Re: MULTISET Vs SET tables |
| |
| From: | | Dieter Noeth |
Coffing Christopher L wrote:
| | That is quite right... Another gotcha that I have seen when creating a table using the "AS SELECT" statement is the Primary Index is not
always duplicated from the source table. Not sure if this is a feature but I make sure that I always define the Indexes and do not rely on the
Defaults. | |
If it's a "create table as (select...)" then all index information is lost and the defaults are used -> the first column will be a
NUPI.
Index information is also lost when "create table as" includes any index definition or Primary Key/Unique constraint.
The problem with set/multiset has been fixed, but i can't remember exaxtly when, at least V2R5.
Btw, when you "create table as (select...)" then the session defaults are used, i.e. Set for Teradata and MultiSet for ANSI session.
Dieter
| 
