Ø I just dont see any good reason to use the attribute list.
As a personal style or standard, you might choose not to override column names
in the attribute list – but if you are extracting DDL for an existing view then
you are at the mercy of whoever wrote that view.
i.e. if the original author wrote
CREATE OR REPLACE VIEW V (DOG) as SELECT DUMMY AS CAT FROM DUAL;
Then you definitely need the column specification to correctly re-create the
view.
Mike Tefft
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Fergal Taheny
Sent: Tuesday, April 25, 2017 4:47 PM
To: Powell, Mark <mark.powell2@xxxxxxx>
Cc: Michael D O'Shea/Woodward Informatics Ltd
<woodwardinformatics@xxxxxxxxxxxxxxxx>; jeff.d.smith@xxxxxxxxxx;
oracle-l@xxxxxxxxxxxxx
Subject: Re: SQL Developer - view DDL Formatting
Hi Mark
I am of the opinion that views should always have an attribute list since I
have encountered views where the view column name does not match up to the
select list column names.
Nor should a new column added to a table automatically appear in any views
defined on the table. The sensitivity of the column data has to be considered
in relation to the purpose and audience of each view that references the table.
When the view is updated you can easily generate the view code from the RDBMS
Dictionary or using DBMS_METADATA.
