Re: sysibm.sqlcolumns column_text Corrections -- WEB400

Subject: Re: sysibm.sqlcolumns column_text Corrections
From: CRPence <crpbottle@xxxxxxxxx>
Date: Wed, 02 Dec 2015 12:04:53 -0600
List-archive: <http://archive.midrange.com/web400/>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: "Web Enabling the IBM i \(AS/400 and iSeries\)" <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

On 02-Dec-2015 09:54 -0600, Buck Calabro wrote:

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

Microsoft /owns/ the ODBC specs. I checked, and the SQLCOLUMNS VIEW matches the specs; any column after the 18th can be system-specific, and why COLUMN_TEXT can be there, so there is little reason why the SQLCOLUMNS could not be re-created [if properly managed with System Change Management, if done by the user vs the OS] to include the COLUMN_HEADING column from an underlying\based-on SYSCOLUMNS VIEW just like is done with COLUMN_TEXT.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: sysibm.sqlcolumns column_text Corrections , Buck Calabro

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.