HP3000-L Archives

September 1997, 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:
From:
Curt Brimacomb <[log in to unmask]>
Reply To:
Curt Brimacomb <[log in to unmask]>
Date:
Fri, 5 Sep 1997 11:19:35 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (40 lines)
Yes, but you can get the end of chain record number (stat7-8) on the dbfind and then start reading backwards.

Curt Brimacomb
System Manager                                          www.magiclink.com
Idaho Computer Services, Inc.                                   Voice:  1-208-734-2245
Twin Falls, Idaho 83301                                         Fax:    1-208-733-9663


-----Original Message-----
From:   Michael A. Dobies [SMTP:[log in to unmask]]
Sent:   Friday, September 05, 1997 9:35 AM
To:     [log in to unmask]
Subject:        Re: Image Inefficient?

Don't you have to go to the endof chain, before you can go backwards?

Michael Dobies

-----Original Message-----
From:   Gary Groves [SMTP:[log in to unmask]]
Sent:   Friday, September 05, 1997 7:49 AM
To:     [log in to unmask]
Subject:        Image Inefficient?

I need to create a new Image dataset. I want to retrieve the records in
reverse date order (LIFO). I was going to do a backwards chain read.
Someone told me that a reverse chain read was not efficient.

For other design reasons, I've decided to use a composite Omnidex key,
but I'm curious if the above is true. If so, Why?

Gary Groves

Kwestions, Kwalms, Kweries, Komments....Kall!


http://www.superstar.com
http://www.netlinksat.com
http://www.uvsg.com

ATOM RSS1 RSS2