RE: estimating RGZPFM runtime -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: RE: estimating RGZPFM runtime
From: rob@xxxxxxxxx
Date: Wed, 20 Nov 2013 07:04:32 -0500
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/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Maybe we're trying to solve the wrong problem. Instead of waiting for the
horse to get out of the barn to do something why not close the barn doors?
Write a trigger program that if the user isn't JOELS then they are not
allowed to change the primary key. Why worry about it afterwards?
Although I do get a jolly out of kneecapping someone who did something
they're not supposed to.
Granted, if you throw up an error in the trigger and it's canned vendor
software which doesn't for a write error it's going to get ugly. But, by
golly, it will drop it quicker than a chipmunk vs a .50 cal.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2026 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.