|
Has advantages and disadvantages. I've fixed a few bugs (some were even mine) where identically named fields had different values. It's a real advantage when you're doing sequential i/o and writing updated values from the input file to an output file that has the same record format. All in all, I really like prefixes. -----Original Message----- From: Rob Berendt [mailto:rob@dekko.com] Sent: Tuesday, May 04, 1999 7:46 AM To: MIDRANGE-L@midrange.com Subject: Same field names Not to start a holy war, but here goes... Our accounting package uses the same field names in all of their files. For example in the files EMPNAM, EMPJOB, etc, the employee number field is EMPLY. Prior to RPG ILE, this was a minor pain because you had to rename all the fields by hand. With ILE RPG you just use the PREFIX keyword and the rename is done quick. But, here is the cool part. Query the file QADBIFLD on your system and you can see every file containing this field. Since this file is 1.4GB on our system I thought I'd might as well use it. So what do you think of using the same names? How about requiring database field names be limited to 7 or 8 characters so the PREFIX keyword is cleaner? +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.