Hi,


RD> Another thing I do when I need large searchable varchars it to have
RD> second OCTETS field. Each time I insert or update a string in the field,
RD> I create an MD5 and store it in the OCTETS field. Then I just use this
RD> for searching. Seems to work well. Usually, inserting or updating is the
RD> result of a user action, so I don't mind the hit required to generate
RD> the MD5. Anyway, MD5 creation is pretty fast. This is usually better
RD> (and more unique) than using a substring.

Cool idea!
I think I'll try.


Björn


--