On Wed, 15 Dec 2004, EP wrote:
> Thomas Spahni <[EMAIL PROTECTED]> wrote:
>
> > the column type will limit the number of characters per row. A column
> > of type TEXT will hold up to 65,535 characters but with LONGTEXT you
> > can put up to 4,294,967,295 charcters into one row. I have an
> > application with Texts of up to 200 pages in one column. Full-Text
> > Search is handling this very well.
>
> Thanks...
>
> Really?! If I can follow-up with another question, does experience
> suggest Full-Text Search handles a large number of such documents
> efficiently? For example, I am expecting to have (up to) one million
> documents in my database. I was considering breaking each document into
> paragraphs for search efficiency, but if Full-Text Search can search
> return results quickly on a large number of "long" (e.g. 10,000+
> character) documents, my database has just become much simpler.
>
> Eric
My average document is 16700 bytes long and I have 21'649 of them (number
growing).
I can give you an example how slow (fast) it is:
mysql> select count(*) from unpublished where match (bgetxt) against
('Garten Waldbaum Gutachten');
+----------+
| count(*) |
+----------+
| 2841 |
+----------+
1 row in set (1.97 sec)
mysql> select count(*) from unpublished where match (bgetxt) against
('Willensvollstrecker');
+----------+
| count(*) |
+----------+
| 34 |
+----------+
1 row in set (0.03 sec)
This is on modest hardware (single P4, 1GB Ram, SCSI drive). My index
still fits into RAM but was not buffered for the first query above. I
would definitely try to keep your texts in a single piece each.
Thomas Spahni
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
