Re: Stored procedure column names -- 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.

Subject: Re: Stored procedure column names
From: Justin Taylor <jtaylor.0ab@xxxxxxxxx>
Date: Tue, 3 Jan 2023 12:33:18 -0600
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

There isn't a SELECT statement.

The stored procedure does a SET RESULTS SETS.
https://www.ibm.com/docs/en/i/7.5?topic=statements-set-result-sets

The client does a CALL.
https://www.ibm.com/docs/en/i/7.5?topic=statements-call

date: Thu, 29 Dec 2022 14:39:25 -0600

from: Javier Sanchez <javiersanchezbarquero@xxxxxxxxx>
subject: Re: Stored procedure column names

Try forcing them to lowercase, i.e.:
SELECT COL_A as "col_a"...
Make sure to enclose them in doble quotes.

Try that and let us know.

JS

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Stored procedure column names , Javier Sanchez

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.