The way I really hoped would be implemented was to have the index
files exist within the file subdirectory, i.e. all files with
indexes
would be similar in structure to Type30, but have a .index
subdirectory within them. So, from then on, the indexes would be
tied to the main data
IBM could help us here by writing a backward link in the I_INDEX.MAP
that says where the primary file is that the index supposedly
references. If there is a mismatch, error out.
Is there a situation where the current state, where more than one
primary files could point to the same index is a
Funny you mention this. Back in 1994-95 when I was rewriting all the low
level indexing code, we tried to figure out some way to do exactly this,
putting some type of full path or such within INDEX.MAP to point back to
the main file. Problem is, we couldn't figure out a way to safely do this
:[EMAIL PROTECTED] Behalf Of Glenn Herbert
Sent: Monday, August 02, 2004 12:31
To: [EMAIL PROTECTED]
Subject: RE: [U2] RE: Copying data between two Universe servers
Funny you mention this. Back in 1994-95 when I was rewriting all the low
level indexing code, we tried to figure out some way to do
Another trap for the unwary
If you use an operating system copy program to move a UniVerse file that has
alternate key indices, the index subfile pathname stored in the file header
will not be updated. You may need to use SET.INDEX to correct this after
the copy.
I know of one major UV user
