On Wed, 28 Jun 2000, Geoff Hutchison wrote:
> On Wed, 28 Jun 2000, Bill Carlson wrote:
>
> > What is really needed (and has been discussed before) are tools to "dump
> > and reload" the ht://Dig databases, so that the indexes can be easily
>
> Well, this is implemented as of 3.2.0b2. It's more reliable as of the
> current snapshots since a few bugs were fixed.
Cool! Yet another reason to check out 3.2 as soon as I get time...
> In an ideal situation, this also allows you to change database formats (if
> you wanted to use SQL or some fancy new research database code or
> something) or in case ht://Dig 3.3 introduces a slightly different
> database format.
I whole-heartedly agree, it would be fantastic if one could run whichever
database one chooses. But the argument in the past has been that the
current code is entirely optimized and entwined with BD, making it a huge
undertaking to do.
> RAID over IDE? I'd personally go with SCSI drives, but I digress.
Head over to www.3ware.com and read their discussion on IDE vs SCSI. I run
SCSI myself, but I think IDE is ready to go with some of the new
controllers and certainly a lot cheaper. 40GB for $180, kind of hard to
beat.
> However, I'd love to see the "flow" be much simpler. Ideally, the digging
> and searching could be performed at the same time. Then you'd only need
> one copy of your databases and you could keep the digging going much more
> frequently if you desired. You could still do a dig-and-update cycle if
> you wanted, or you could do this. There are benefits and drawbacks to both
> strategies.
Yeah, that would be nice as an option. But it's not really a 'gotta have'.
> (For example, if you only have one copy of your databases and something
> gets corrupted, you're dead for a good long time.)
And you should be shot for having only one copy anyway...:)
Bill Carlson
------------
Systems Programmer [EMAIL PROTECTED] | Opinions are mine,
Virtual Hospital http://www.vh.org/ | not my employer's.
University of Iowa Hospitals and Clinics |
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
