RE: Add fields to physical file without exclusive lock _ formerly Re: Stupid question of the century

You couldn't add the read trigger without an exclusive lock anyway.

Mark Walter
Business to Business Data Integration Specialist
Certified IBM System i Specialist
Paragon Consulting Services, Inc
mwalter@xxxxxxxxxxxxxxx
717-764-7909 ext. 126


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Monday, May 11, 2009 10:04 AM
To: Midrange Systems Technical Discussion
Subject: Re: Add fields to physical file without exclusive lock _ formerly Re: Stupid question of the century

That strikes me as a very bad idea.

My understanding is that read triggers should be avoided unless
there's no other way to do what you want. Example: for legal reasons,
you need to track who's read what rows in a certain tables.

The extension table is a good idea, I'd simply create the extension
along with an SQL view and/or joined logical.

Charles

On Mon, May 11, 2009 at 9:53 AM, Albert York <albertyork@xxxxxxxxx> wrote:

Here is what I would do.

Add the extra fields in extension files.

Add a read trigger to the main file. Have the trigger program read all of the extension files and put the data in the LDA.

Only the programs which require the additional data have to look at the LDA.

Albert

----- Original Message -----
From: "Douglas Handy" <dhandy@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Subject: Re: Add fields to physical file without exclusive lock _ formerly Re: Stupid question of the century
Date: Mon, 11 May 2009 09:40:34 -0400


Alan,

I found it interesting that you no longer recommend this method any more.

Can you say why

Two obvious things: SQL and Query do not understand the subfields.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.