Re: A question for Mr. Celko
Date: Mon, 19 Jul 2004 14:05:01 GMT
Message-ID: <hyQKc.132441$XM6.88387_at_attbi_s53>
"Jan Hidders" <jan.hidders_at_REMOVETHIS.pandora.be> wrote in message news:pan.2004.07.19.09.35.30.941204_at_REMOVETHIS.pandora.be...
> On Mon, 19 Jul 2004 04:08:48 +0000, Marshall Spight wrote:
> > "Jan Hidders" <jan.hidders_at_REMOVETHIS.pandora.be> wrote in message
> > news:pan.2004.07.19.00.19.32.644229_at_REMOVETHIS.pandora.be...
> >>
> >> That's a physical layer problem and the ideal database should let you
> >> choose the right data structure for the mix of updates and queries that
> >> you expect.
> >
> > (Actually, I would propose that the *ideal* database would measure the
> > updates and queries it is receiving and choose the right data structure
> > itself.)
>
> Sure, but let's first try to take a few small steps before we see if we
> can run, ok? :-)
'Sokay. Although I generally prefer to set out on a mad sprint even before warming up.
> >> So the question is not "what is the best data structure" but "what data
> >> structures are there" and in which case should we use which data
> >> structure.
> >
> > Okay. So I'll ask: what data structures are there?
>
> For lists? That's a whole research field in its own. You really expect me
> to give a short summary of that here?
A brief mention of some alternatives by name gives me something to google for.
> There are whole conferences
> dedicated to optimization in list-manipulating languages.
Marshall Received on Mon Jul 19 2004 - 16:05:01 CEST