Re: Identity columns and RLA -- RPG400-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: Identity columns and RLA
From: dlclark@xxxxxxxxxxxxxxxx
Date: Wed, 31 Aug 2016 18:36:10 -0400
List-archive: <http://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 08/31/2016 05:03:05
PM:

Thanks Vern. I'm thinking I'll change the program to just use SQL for
everything, since it's simpler. But I was curious about mixing RLA and

SQL.

There is a way that you can associate a null indicator with an RLA
field so that you have control whether an identity value is generated or
you set your own. However, generally, you let the database generate
identity values on WRITE and keep the current identity value for UPDATE.

Sincerely,

Dave Clark

As an Amazon Associate we earn from qualifying purchases.

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.