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



I thought about this before and, yes, there are other SELECT * queries on
these tables. But I wondered about using ALTER to change this on the fly:
Alter table xyz Alter column IQXSEQUENC SET implicitly hidden
Insert using fullselect
Alter table xyz Alter column IQXSEQUENC SET not hidden

This actually works, but the ALTER needs an *EXCL lock (makes sense).
While, normally, this would not be a problem, I don't want to chance that
someone else is querying the file when my application attempts to do the
ALTERs, causing SQL0913.

- Dan

On Thu, Aug 17, 2017 at 3:12 PM, Darren Strong <darren@xxxxxxxxx> wrote:

One possible solution is to define the column as IMPLICITLY HIDDEN, but I
don't know if you have the ability to change the column definition at this
point, or if it would cause problems where programs are expecting to see
this field if they select * from the file.


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.