Re: Comp.archives database format

Article View: comp.archives

Article #5547

#5547

From: Eric Schwarz
Date: Wed, 26 Oct 1988 20:34

18 lines
1163 bytes

I've got a question and possible problem for you concerning the
database format.

Is there a reason why you are using different field delimiters for
the 3 database entry formats?  The site entry uses colons, the
information entry uses commas (with colon sub-field delimiters), and
the content entry uses semi-colons.

The site entry contains a path to the archive files, what about
archives that have multiple archive directories?  You need to know
which files are in which directories.  Is putting this information
in the content entry going to make it too big (I don't know how
many content entries there will be eventually)?

Apart from these two items, it looks pretty good.

Eric Schwarz
uunet!edg1!grumpy

Technical Details

Message-ID: <275@edg1.UUCP>

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!uflorida!novavax!proxftl!twwells!comparc

References: <116@twwells.uucp>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!uflorida!novavax!proxftl!twwells!comparc
From: grumpy@edg1 (Eric Schwarz)
Newsgroups: comp.archives
Subject: Re: Comp.archives database format
Message-ID: <275@edg1.UUCP>
Date: 26 Oct 88 20:34:35 GMT
References: <116@twwells.uucp>
Sender: comparc@twwells.uucp
Organization: Edison Design Group, Inc., Edison, NJ
Lines: 17
Approved: bill@twwells (T. William Wells)

Reply to Parent Message