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



Ah, but does one REALLY need to create the view or index which omits this
field in order for it to be updated automatically even by RPG RLA? Keeping
in mind that the original thought was that if you do not then RLA will
slap an initial value in there. One workaround was to use the initialize
with external default. But what about:
IMPLICITLY HIDDEN
Indicates the column is not visible in SQL statements unless it is
referred to explicitly by name. For example, SELECT * does not include any
hidden columns in the result. A table must contain at least one column
that is not IMPLICITLY HIDDEN.

I suppose the rub here is "... in sql statements...". RLA is not SQL. So
I can't
CREATE TABLE ...
(...,
LastUpdated timestamp generated always for each row on update as row
change timestamp implicitly hidden,
...)
and expect it won't be initialized to 0001-01-01... by RLA, because RLA
does not respect "implicitly hidden", true?

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.