Unless it's a sort item, I put it at the end to avoid problems UNLESS this is a new dataset and recompiling everything that uses it is easy because I know what those program(s) are. In that case I'll put it where it logically belongs.
mike
>>> "F. Alfredo Rego" <[log in to unmask]> 5/22/2008 12:28 AM >>>
At 8:28 PM -0700 05/21/2008, Walter J. Murray wrote:
>Greetings,
>
>This question came up during a discussion with our Database
>Administration group, and I thought I'd poll the -L to see if there were
>any consensus.
>
>When adding an item to a data set using one of the fine TurboIMAGE
>maintenance programs, you have a choice of where to add it.
>
>Do you:
>
>1. Generally always add it at the end, on the theory that it is least
>likely to cause a problem there? Or,
>
>2. Insert it wherever would seem most logical, maybe even keeping your
>items in alphabetical order within the data set?
>
>I'm just curious about common practice.
I don't know too much about "common practice" but here are some
uncommon thoughts (about field layouts for datasets, and about
the various flavors of access lists) that you may find
intriguing and, hopefully, relevant to your questions:
http://www.adager.com/TechnicalPapersHTML/ImageDBfoundations.html
Look for the paragraph entitled "Access lists" (towards the end
of the paper). Start reading there and be sure to also study the
next few paragraphs.
I wrote that a very long time ago, but I believe the ideas are
timeless.
Enjoy,
_______________
| |
| |
| r | Alfredo http://www.adager.com ( http://www.adager.com/ )
| e |
| g | F. Alfredo Rego
| a | Manager, R & D Labs
| d | Adager Corporation
| A | Sun Valley, Idaho 83353-3000 U.S.A.
| |
|_______________|
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
