Re: sysibm.sqlcolumns column_text Corrections -- WEB400

× 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 12/1/2015 5:25 PM, CRPence wrote:

On 01-Dec-2015 10:55 -0600, Vernon Hamberg wrote:

<<SNIP>>
You may have seen my post where I recommend NOT using SQLCOLUMNS,
rather, to use SYSCOLUMNS.

Yes. Both you, and Buck. But that could be somewhat like saying "Use
C" to an RPG programmer; I do not recall clarification by the OP as to
why one is being used vs another, or if any followup ruled-out or
confirmed that was an option for them.

It seemed logical to suggest that a developer wishing to read IBM
i-specific catalogue information use the IBM i-specific catalogue, where
COLHDG() is surfaced.

I suggested another approach [though I would not recommend
vociferously], to customize that VIEW. or to ask for a clarification or
possible /correction/ regarding what the SQLCOLUMNS VIEW offers, because
the ODBC specs were updated to include something more in SQLColumns()
API than is apparently being included in the VIEW SQLCOLUMNS.

I wonder if there is some standards body which determines the columns
that SQLCOLUMNS ought to have.

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.