-Original Message-
From: Bret Ewin [mailto:[EMAIL PROTECTED]]On Behalf Of Bret Ewin
Sent: Monday, January 21, 2002 12:03 PM
To: 'Russell King'
Subject: RE: Help with Database structure..
You may also want to break the URL into pieces (protocol, domain, path,
file) and index each piece
Noah,
Sunday, January 20, 2002, 1:55:00 AM, you wrote:
NS The problem is that 20,000 tables can be a bit unwieldy for mysql to
NS handle.
I don't think it will be a sore work for MySQL to support more than 20,000
tables, but it's up to a inode limit on the filesystem on your OS.
As Russel
I need some help with a database design question:
To summarize our design (I'll spare you a lot of the details.)
We collect text files from 20,000 different sources every day. The actual
file is stored as a text file. Each source has its own table which contains
a list of the text files,
We thought about having one massive file for all this data, BUT, we
archive
something like 100,000 articles a day. We store articles for 6 months, so
this table would very quickly have 18,000,000 rows. Now, we need to
select
a group of articles based on source and date. We also need to
