34 lines
1.2 KiB
Plaintext
34 lines
1.2 KiB
Plaintext
From: pchristo at ic.sunysb.edu (Pavlos Christoforou)
|
|
Date: Tue, 13 Apr 1999 14:13:14 -0400
|
|
Subject: simple indexed file module?
|
|
In-Reply-To: <7evg0s$spu$1@nnrp1.dejanews.com>
|
|
References: <joe-120419991008353558@chinacat.salk.edu> <7evg0s$spu$1@nnrp1.dejanews.com>
|
|
Message-ID: <Pine.SOL.3.96.990413140918.24975D-100000@sparky>
|
|
X-UID: 392
|
|
|
|
On Tue, 13 Apr 1999 aaron_watters at my-dejanews.com wrote:
|
|
|
|
> In article <joe-120419991008353558 at chinacat.salk.edu>,
|
|
> Joe Strout <joe at strout.net> wrote:
|
|
> > For a CGI script I'm working on, I need to keep a couple of indexed
|
|
> > files. These will contain variable-length data (descriptions), which
|
|
> > may be changed fairly frequently. So I imagine that in addition to the
|
|
> > data file, there will be an index file that keeps track of the position
|
|
> > and length of each record. New or expanded records will be stuffed in
|
|
> > wherever there is free space, or at the end if no sufficient free chunk
|
|
> > is available.
|
|
>
|
|
|
|
I would suggest you use BoboPOS, the Object database used in Zope and
|
|
available as a seperate component. It supports transactions, multiple
|
|
versions and undo plus a lot of other cool things. It is very easy to use
|
|
and very stable.
|
|
|
|
Pavlos
|
|
|
|
|
|
|
|
|
|
|
|
|