HP3000-L Archives

September 1997, Week 2

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:
Cortlandt Wilson <[log in to unmask]>
Reply To:
Cortlandt Wilson <[log in to unmask]>
Date:
Wed, 10 Sep 1997 09:20:14 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (19 lines)
The recent discussion on sorting brings to mind Dr. Codds dictum in the
relational model that     entries can be stored in any order -- this
greatly simplies design as the recent discussion proves.

In the ideal world perhaps IMAGE would return data via a sorted DBGET.

As I understand the IMAGE internals, maintaining a sort field has almost no
performance impact IF entries are added in sorted order.   Is this correct?


Given all the programmer time and concern over maintaining a sort order in
chains perhaps it would be cost effective and even considered to be good
database design practice to declare sort fields when data is added in sort
order.

--
- Cortlandt Wilson
  Cortlandt Software    (415) 966-8555

ATOM RSS1 RSS2