Kevin King wrote: > I can't say for certain that it would work at all, but if it did I > would wonder if performance would be as good as a properly sized > hashed file. Why would you want to change this to a directory?
Hi Kevin,
Thanks for your reply.
I have tested this and found that it appears to work at least on initial inspection. In other words, I can put a paragraph into a DIR type file, create an R-type VOC pointer, and then run or PHANTOM the paragraph. I don't know what the performance impact would be. In the little bit of testing I did, I didn't detect a noticeable difference. The DIR-type file I used for the test has 1863 items in it. I'm not sure what else might be worth testing. Is there a specific usage scenario that you think might be prone to performance problems?
In answer to your question, the reasons that I want to change our VOCLIB files to a directory are:
- I want to use jEdit to edit the paragraphs.
- I can see the date and time of last update of a paragraph.
- I can use the unix find utility to identify paragraphs that have not been accessed in a long time to assist with clean up.
- I can recover individual files from tape backup instead of the whole UniData file (date and time stamp on individual files would help here as well.)
- I can apply Unix-level permissions to individual paragraphs to control access.
- It would be nice not to have to keep resizing VOCLIB files. It's difficult to keep up with everyone writing paragraphs. I should note that in our environment we don't use the default VOCLIB file itself, but rather create a custom file (e.g., XJXM.VOCLIB) for each person writing paragraphs. Each file needs to monitored and adjusted.
- Our voclib files tend to be hard to size. They also don't have even growth--people can quickly overflow the files by copying records in.
Thanks again, Josh ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
