HP3000-L Archives

June 2002, Week 4

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:
"Jonathan M. Backus" <[log in to unmask]>
Reply To:
Date:
Wed, 26 Jun 2002 08:42:24 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (60 lines)
Jim,

        Personally I would say it would depend on the nature of the data, meaning
the amount of data and how you intend to use it.  For example, there is the
spell checker thread that was recently on the list.  The most likely
solution was to compare the words in the new data against a list of
correctly spelled words.  The list of words is "static", but very large and
the intended use to not have all of them in memory, but rather to access
just the words that are included in the new data.  Clearly this example
lends itself towards storing the static data in a database.  On the other
hand, if you just have a small amount of static data, then you may want to
maintain it in a flat file for simplicity.

Thanx,
        Jon

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
Behalf Of Jim Phillips
Sent: Wednesday, June 26, 2002 8:26 AM
To: [log in to unmask]
Subject: [HP3000-L] Storing Static Data


Okay, here's my on-topic post for the month!

We have occasion to store "static" data (and by that I mean data that may
change only infrequently, if ever, things like the skid deposit charge or
the minimum charge for rework, etc.).  Now, I dislike making these items
constants in a program since that requires me to change the program and
recompile it if the "static" data does, in fact, change.

So, I've sometimes seen this type of data stored in a "flat" file,
especially if it's "control" data of some kind that pertains to only one
program or set of programs.  However, I've also seen this type of data
stored in an Image data set (usually a master data set that has as a key
some kind of control-id or sequence number), especially often-changed static
data, like the next sales order number, but also for lesser-changed static
data, like the current copper cost which only changes once a month.

Anyway, my question is this:  Does it make more sense to store this data in
an Image data base where it is more "protected" (my impression only, is it
really?) rather than in a "flat" file, which, by implication, is less
well-protected?


Jim Phillips                           Information Systems Manager
Email: [log in to unmask]     Therm-O-Link, Inc.
Phone: 330-527-2124                         P. O. Box 285
Fax:   330-527-2123                           10513 Freedom Street
Web:   http://www.tolwire.com          Garrettsville, OH  44231

I WANT MY MPE!

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2