I think that is absolutely a bad idea. Not only are you splitting data
that should logically be together, you will need to add three indexes
and perform three searched to get at the data. You typical index only
indexes from the start of the field, so even if you split the data, you
can't do contained in searches that will use an index.
Keep in all in one text field and use a full text index. If you need to
index the first 20 characters or something for quick sorting, than also
add a regular index on the field. But a full text index on one field is
what you want to use.
On May 23, 2005, at 2:02 PM, Scott Purcell wrote:
After some thought into this, I believe that I may actually need to
eventually "search" this field, and may need an index on it. After
talking to others at the office, they think that maybe I should try
and create three varchar(254) fields and tie them together. Therefore
I can have a larger description field, and still be able to index. Is
this a bad or crazy idea? I have never heard of doing this, but I can
via code, show the results from three tables and concat it together?
Any ideas, thoughts .... I figure I need about avg: 1000 characters
per description.
Thanks,
Scott
--
Brent Baisley
Systems Architect
Landover Associates, Inc.
Search & Advisory Services for Advanced Technology Environments
p: 212.759.6400/800.759.0577
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
