Can't find FULLTEXT index matching the column list

I'm getting the error:

"Can't find FULLTEXT index matching the column list"

I have found that the column list in my query must EXACTLY match the column list in my FULL TEXT index.

So if I want to query like this:

SELECT FileID,'File'
FROM FileMetaData
WHERE MATCH (FileText,OrigAuthor,LastModAuthor,Description,Custom5Value)
AGAINST ('one for the money')

. . .I must create my fulltext index like this:

CREATE TABLE FileMetadata (
  FileID int(11) NULL,
  FolderID int(11) NULL,
  ProjectID int(11) NULL,
  FileText text NULL,
  FileTextPage int(11) NULL,
  OrigAuthor varchar(50) NULL, #mandatory metadata field
  LastModAuthor varchar(50) NULL, #mandatory metadata field
  Description varchar(100) NULL, #mandatory metadata field
  Custom1Value varchar(50) NULL,
  Custom2Value varchar(50) NULL,
  Custom3Value varchar(50) NULL,
  Custom4Value varchar(50) NULL,
  Custom5Value varchar(50) NULL,
  FULLTEXT KEY idxFileMetaData (FileText,OrigAuthor,LastModAuthor,Description,Custom5Value)

. . .but this is not practical for me, because any combination of those fields can be searchable by a user. My UI allows users to select which fields to search against. If their selection happens to not correspond with the exact fields as specified in the fulltext key, I get the error mentioned above. Even if I include EVERY text-like column in the table, in the fulltext index, if the user wants to search only against a subset of those columns, the error will result.

It's hard for me to believe that MySQL 4.1 could possibly be this inflexible. . .? I must be doing something wrong. How can I include all text-like columns in my fulltext index, but still allow users to search against any desired subset of those columns?

Or is there some trick for an alternative? I guess if i had to query against all columns every time, is there a way for me to exclude records that matched against columns that the user did not want to include in the search?
LVL 11
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I think you can use a fulltext  for each field and just union them.
I don't think you have any other alternative.  
There's no such thing as partial indexing (e.g. using less than all of the fields that compose an index)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SweatCoderAuthor Commented:
yes, i came to that conclusion as well. i had to make a separate index for each field, and then in my queries, specify a single field for each query and do a bunch of unions.

this is a real flaw in mysql. it's very rigid and allows no flexibility in the way the sql is written, and thus how the app is developed in this sense.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
MySQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.