Profile input interest error.

If you put in SQL as an interest in your profile it causes major errors and won't allow your profile to be saved. This tells me that the String error handling is not that robust. When I removed that SQL term it worked again.

Start by reproducing the profile save failure with SQL entered as an interest, then trace the String error handling involved in saving profile input. Done means a profile containing SQL as an interest saves successfully without the reported errors.

Written by the indexing model from the issue text.