× 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.



On 02-Jun-2016 14:30 -0500, Dan wrote:
As far as I can tell from the documentation, I am unable to exclude
from a View definition just one field from the table on which the
view is created. i.e.:

create view testlib/testtrv001
as select a.* EXCLUDING FIELD123 from testtrg001 a

"EXCLUDING FIELD123" is my pseudocode to indicate that I want all of
the fields in testtrg001 *except* FIELD123 included in the view
definition.

I know I can just list all 423 fields (less FIELD123) from the
testtrg001 table in the select, but taking a poker in the eye seems
preferable.

Pipe dream?

I know that many times I have lamented the lack of the capability in the SQL, to effect directly an /omit/ or /exclude/ of some named columns from a select-list\column-list per the use of SELECT *, whether for example, that be in the query of a CREATE VIEW or an INSERT. But, I could not find any past discussions... until just now, after I recalled where I had created a routine to effect the omission of one column:

Here is a link to an example helping to /solve/ that issue [similar to as alluded by Buck] somewhat generically; NB: I incorrectly refer to the routine as the "VIEW_ON procedure", wherein later in the scripted code I issue "create procedure view_of /* not functional for TABLE files in QTEMP! */":
[http://archive.midrange.com/midrange-l/201305/msg00083.html]


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.