What about those HUGE tables?
| From: | Trond Erling Hundal | Date: | Fri, 08 Dec 2000 07:35:49 +0000 |
| Subject: | What about those HUGE tables? | ||
| Groups: | php.db | ||
| Request: | Send a blank email to php-db+get-5092@lists.php.net to get a copy of this message | ||
Hey there...
I`m writing news to a database, thats has several main-pages that displays
10 - 20 articles on every page.
One article can be shown on several main pages.
The way I`ve organized this, is to store the articleid and the pageid in a
"relation-table"
But, after a certain amount of time this table becomes HUGE!
So far those relations that no longer beeing shown on any pages are
automatically deleted.
But, now I am working on a concept for a entirely new set of pages that
require ALL the relations
are ALWAYS in the relation table, in order to be able to search in this
spesific "category."
So. I am making a new relation table, but I am afraid that this table also
will become HUGE and unmanagable.
Will the "index" of "articleid" be sufficient, or do I have to start
thingking about alternativ solutions?
-TrOnd-