× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



This is easily done. Very easy.
First, take your DDS and throw it into the ashcan. Use DDL instead.
Second, on your base table define the undesired column as implicitly
hidden. Then when anyone does a
select * from basetable...
The 'hidden' column will not be included. They will have to explicitly
ask for it.
select a.*, a.FIELD123 from basetable a ...
So, when you create the view it will not include the implicitly hidden
columns.
QED.


If you just HAVE to stay with DDS and you totally want to blow change
management out of the water try this:

CRTDUPOBJ of your existing table to TEST

then
ALTER TABLE TEST
ALTER COLUMN FIELD123 IMPLICITLY HIDDEN

SELECT * FROM TEST
and you will not get the column FIELD123

To change it back
ALTER TABLE TEST
ALTER COLUMN FIELD123 NOT HIDDEN



Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.