Re: Min authority for foreign key table -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

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

Subject: Re: Min authority for foreign key table
From: Rob Berendt <rob@xxxxxxxxx>
Date: Fri, 13 Jul 2018 13:00:47 -0400
List-archive: <https://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: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Interesting. At first I wondered why any authority at all would be
needed. Then I got to thinking. If I had a parent table with a key of
A0010 and the text was "Top secret covert operations". And I tried to
change that key and it rejected it because I wasn't allowed to even know
if there were any projects in the ActiveDeployment table tagged "Top
secret covert operations".

I would try ensuring that your reads ARE reads only. For example
select ... from ... for fetch only

Rob Berendt

Follow-Ups:

RE: Min authority for foreign key table , Justin Taylor

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.