[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gne]API

From: Hook
Subject: Re: [Bug-gne]API
Date: Thu, 28 Jun 2001 23:00:26 +0800

Tom Chance wrote:

> >The body of large articles too? Oh well, it's not my system. Be aware
> >though, that once the API gets designed you may end up locking the
> >structure into something pretty close to what you're proposing now, and
> >after 6 months or so, you might find excellent reasons for redoing the
> >schema. That always has fallout which affects all the scripts which
> >the data. It could be expensive.
> Well the other solution was to put all the bodies into text files and have
> extra field in the database to link to that text file - in effect using
the database
> as a search index. But opinion has been a bit divided as to whether or not
> putting the body in the db will slow down or lock up the db.

You're right, it is the viable alternative. My experience with databases
suggests that putting large blocks of data into a single row always gives a
performance hit. BTW, if you're considering MySQL's full text indexing, be
aware that it can be *enormously* slow.

Database design is a complex field, more so if you want to build something
which will give good performance as the number of concurrent users climbs.

The Hooker

reply via email to

[Prev in Thread] Current Thread [Next in Thread]