 |
 |
Archives of the TeradataForum
Message Posted: Tue, 04 Feb 2014 @ 10:31:44 GMT
Subj: | | Re: 1:1 Views - Sel * from Table OR SELECT all columns from table |
|
From: | | Gorner, Tomas |
| If we create the views using 2nd procedure (listing all columns), whenever a column is added/dropped in a table, we will have an idea to
modify the underlying views. | |
True, but you will then have to go into the view's DDL and add the column nominally. Whereas, when using " SELECT * ", you can just run
blindly the view's DDL every time you add a column to the underlying table. One operation less to do, you just need to make it a norm, that after
a certain change to a table's DDL, the view's DDL has to be executed as well.
| But, there will be a wrong assumption, by seeing the statement 'sel * from' in a view, that, the columns/data will be selected from
the table during runtime. | |
To see which columns are listed by the " SELECT * " view, you can always execute "HELP VIEW" statement or query DBC.COLUMNS.
Just my 2 cents.
Cheers,
Tomas
| |