HP3000-L Archives

October 1999, Week 1

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: How to optimally create a KSAM file.
From:
Barry Lake <[log in to unmask]>
Reply To:
Barry Lake <[log in to unmask]>
Date:
Tue, 5 Oct 1999 13:15:12 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (20 lines) 
At 12:53 PM -0700 10/5/99, [log in to unmask] wrote:
>Tracy Pierce writes:
>
>> Use Image for your data, it's SAFE!  Use KSAM for its partial-key lookup
>> - the best feature IMHO.
>
>Not having yet had the opportunity to use it, I'll ask the "obvious"
>question:
>
>        What about the new partial-key lookup (b-trees) in Image?
>
>Is it stable/reliable/etc.?  If so, what remains the "best" use for KSAM?


FYI, partial-key lookups (b-trees) in Image are implemented by using NM
Ksam files in the posix namespace. This seems to me the best use yet for
Ksam files!

Barry

ATOM RSS1 RSS2