On Sun, Feb 9, 2014 at 1:25 PM, Simon Slavin <slav...@bigfraud.org> wrote:
> store two text columns in the table. The first is the text as entered. > The second is your text reduced to its simplified searchable form, > probably all LATIN characters, perhaps using some sort of soundex. Search > on the second column but return the text in the first. > > This allows you to write your conversion routine in the language you're > using to do the rest of your programming, instead of having to express it > as a SQLite function. > Thanks for your reply, Yes. I thought of that as well. I even have the greek soundex() function from a previous implementation. Problem is it will bloat the database considerably, keeping in mind that the users will typically demand that ALL searchable text columns in the application work that way, and who can blame them? And the project manager will not be very keen on accepting both this database size increase and the time needed to calculate the extra soundex column for every database row. It will be much easier to convince this person to accept the time-costly database upgrade needed in both cases (tables need to be recreated to change collation) but not both upgrade and bloat. -- Constantine. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
