×
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 26 Aug 2013 16:50, James H. H. Lampert wrote:
<<SNIP>>
That tells me there's probably something very funky with the
"problem" index. But what would cause an SQL INDEX to show up as
having no members, and to show up in DSPDBR on the based-on physical,
but not in the QDBLDBR API?
An SQL INDEX without a member is an effectively /unsupported/
condition, yet is not a fully prevented condition; i.e. the database
allows and can effect the no-members condition in some non-SQL actions,
but there may be side effects due to the expectations, i.e. some coded
assumptions, that every [non-partitioned] SQL INDEX has its one member.
Note that DSPDBR defaults to "file" relations, not member relations;
i.e. there are multiple capabilities of DSPDBR, to present different
types of relationships. Similarly, what is presented for the List
Database Relations (QDBLDBR) API output depends upon what are its
inputs. Asking for member relations for *ALL members when there are
zero members, for example, should produce no results.
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
