Archive of UserLand's first discussion group, started October 5, 1998.
Indexing in Frontier database - vs sql
Author: Tommy Sundström Posted: 5/13/1999; 4:59:12 AM Topic: Indexing in Frontier database - vs sql Msg #: 6156 Prev/Next: 6155 / 6157
Dave Winer wrote (in Re: Jumping to the topic message:
the odb is ideal for things like DGs. It's hard to imagine how a relational database could be better suited to the job.
While the odb works just as fine as, or better than, an sql database for storing data, it's a bit behind most sql databases when it comes to indexing it.
Every discussion message is for example indexed according to date, in the calendar table. If you manipulate discussion data it's up to you to keep this index in synch. While this is quite possible, and works fine most of the time, it opens up a field of great complexity.
For example: if you happens to delete all the messages for a particular day (by adding a fldeleted = true to them), that day will still be active in the calendar - but there will be no messages to see.
This in itself is not a big problem - but it gives a hint on the problems that will face you if you build a more mission critical indexing, for example on keywords.
Maintaining correct indexes is the key to effective databases, but it's also on of the most complex areas to get right. And at present there is not much support for it in Frontier. (Reservation: I haven't looked into the search engine, obviusly there is a lot of indexing related thinking there, and maybe it can be used to make the odb a realy useful database.)
There are responses to this message:
- Re: Indexing in Frontier database - vs sql, Dave Winer, 5/13/1999; 5:03:39 AM
- Re: Indexing in Frontier database - vs sql, Sam DeVore, 5/13/1999; 7:15:54 AM
This page was archived on 6/13/2001; 4:50:07 PM.
© Copyright 1998-2001 UserLand Software, Inc.