×
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.
Primary keys are not simply unique keys from the DDS created file. A
DDS created file can be assigned primary keys, either via ADDPFCST or
ALTER TABLE ADD CONSTRAINT.
The ability to 'reverse engineer' database files to DDL source is
available via OpsNav Database tools; which uses the QSQGNDDL API. As I
recall that tool [optionally?] generates a primary key definition for a
unique key; i.e. although the unique key defined by DDS is not really a
primary key, it can be represented logically as being so defined just as
alluded is desirable.
The catalog files have the relationship information. Some
information for DDS created files is limited, esp. for keys.
Redirecting to the physical data [of the catalogs, QADB* in QSYS] to
avoid the limits on the catalog VIEW definitions [in QSYS2] that might
eliminate some DDS file attributes, would enable reference to any data
missing from those available catalog VIEWs.
Regards, Chuck
As an Amazon Associate we earn from qualifying purchases.
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
