Re: Using long names -- 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.

On 7/25/2019 2:24 PM, Rob Berendt wrote:

<snip>
It's similar to the folks who use a unique, system-generated number as the actual key for every file. This in theory is freaking awesome, because you can change customer number and every related record will change with it. But it takes a bit more work whenever you're trying to join files together in queries. So often the customer number is attached to a file somewhere and it doesn't get fixed.
</snip>

Which situation are you talking about?

Situation one: CCUST is not the key to RCM (Customer Master). Some hidden uniquely generated column is. The referential constraint between ECH (order header) and RCM would not be CCUST but would be this other key.
Situation two: CCUST remains the key to RCM. However they really start using referential constraints from the database and not just code them in themselves.

Generated keys mean that you can change the primary key *without* requiring database I/O to all of the hundreds (thousands, millions) of records. Even with referential constraints, someone still has to change all those records.

Generated keys means you don't.

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.