×
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 21-Sep-2016 10:55 -0600, Rob Berendt wrote:
I would think a restore is entirely feasible. Another option is to
use iNav and retrieve the SQL source used to create that table.
Another option is to stop using it. Most uses revolved around stuff
like this:
select current time from sysibm.sysdummy1
These can often be replaced with the VALUES or the VALUES INTO
statement
values current time
A distinction with a difference.?:
I expect more appropriate is to suggest that SELECT would be replaced
with the use of a VALUES-clause [aka the _row-values clause\expression_
or values-row] in the query that defines the VIEW. That clause can
generate a derived-table [of one or more rows], in place of a SELECT
that might otherwise be composed to utilize the SYSDUMMY1 in SYSIBM [or
my preference, use the physical table QSQPTABL in QSYS2]. That is to
suggest, the VALUES _statement_ and VALUES INTO _statement_ are
something entirely different, despite the former looking quite similar
syntactically, neither of which can be referenced directly within a VIEW.
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.
midrange.com
