That's pretty much what my patch does. I initially added columns to the albums, contributor and track tables and stored an encoded version there. However, to save changing the schema and simplify the searching I now store both the original (text) and encoded (numeric) versions in the existing 'search' database columns.
This might seem to add a risk of false positives, but because they're encoded numerically unless you've got a lot of artists/albums/songs called "4258646" or whatever you'll not notice the difference! Keeping it all in the one column also means the SQL search remains simple and quick - on my low powered server (~400MHz Celeron), I can't notice any slowdown when lazy searching is enabled. -- hickinbottoms --- Stuart _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
