Re: codd's 12 Rules -- MIDRANGE-L

× 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've not thought much about constraints on tables in QTEMP, but it seems like something that would be problematic. IF this information were to be stored in the catalog, which QTEMP would this apply to? I too can see some possible ways to handle this, but it seems messy, no matter what.

Some questions come to mind.

Local catalog in QTEMP?
Are other SQL objects listed in the catalog?

Stuff like that. I encourage Coy to submit a requirement on the COMMON site or via a DCR if he wants this changed.

Vern

On 5/18/2013 1:17 PM, CRPence wrote:

On 17 May 2013 14:14, Coy Krill wrote:

DB2 on i won't even let you put a constraint on a table in QTEMP,
which drives me a bit bonkers at times.

There are surely a variety of possible implementations that could
enable the QTEMP library to be tracked to the catalogs, thus enabling
constraints to be created into QTEMP. The big issue that is not so
easily, the enabling the capability to query the catalogs [without an
API call to know what to search instead of] using either of the names
QTEMP or SESSION.

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.