Fixed ticket:18 bug reported by John Lara where some database entries would
be continually re-lazified even though they were already lazified. This
resulted in the search columns getting exponentially wider and wider until the
rows got too large and caused SlimServer? to run out of memory. All credit to
the little sqlite library as it seemed to manage rows of over 85MB before the
memory load got too great!
This has probably been around for a long time, and I'm not too sure why it was
occurring as the search looked sound to me (I think it might be a bug in the
Perl database wrapper used in SlimServer? 6.2.x/6.3.x, but I've not got to the
bottom of it to be sure). I've changed the mechanism of searching for items to
lazify to avoid it happening from now on.
Note that this doesn't affect v2.x versions of the plugin for SlimServer? 6.5.
Thanks to John for reporting it and helping to track it down.
