Re: Empty/non-empty field indexing question

Correct. No, there is no point in putting an empty field there. Otis --- "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Hi Otis > > What kind of implications does that produce on the search? > > If I understand correctly that record would not be searched for if > the > field is not there, c

Re: Empty/non-empty field indexing question

Hi Otis What kind of implications does that produce on the search? If I understand correctly that record would not be searched for if the field is not there, correct? But then is there a point putting an empty value in it, if an application will never search for empty values? thanks -pedja Otis

Re: Empty/non-empty field indexing question

Empty fields won't add any value, you can skip them. Documents in an index don't have to be uniform. Each Document could have a different set of fields. Of course, that has some obvious implications for search, but is perfectly fine technically. Otis --- "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>

Empty/non-empty field indexing question

Here's probably a silly question, very newbish, but I had to ask. Since I have mysql documents that contain over 30 fields each and most of them are added to the index, is it a common practice to add fields to the index with empty values, for that perticular record, or should the field be totally