Re: DDL for timestamp column. -- 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: DDL for timestamp column.
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Thu, 24 Aug 2017 18:26:25 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 2017-08-24 12:56 AM, Birgitta Hauser wrote:

RPG doesn't have any way to tell database that some of the fields in the

output buffer should be ignored.
What about using an SQL Index or DDS described logical file without the
fields to be replaced with the default values in the F-Specs with native
I/O?

Yes, that works. But the RPG programmer has to code the F spec to use the index or file. RPG can't create an index or DDS file to use instead of the F spec file.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: DDL for timestamp column. , Birgitta Hauser

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.