2006/12/17, John Tapsell <<a href="mailto:johnflux@gmail.com">johnflux@gmail.com</a>>:<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> At the risk of stating the obvious, but why not just use SQL? select files.filename from files,tags tag1, tags tag2 where <a href="http://files.id">files.id</a> = tag1.fileid and <a href="http://files.id">files.id </a> = tag2.fileid  and tag1.key="artist" and tag1.value="foobar" and tag2.key="group" and tag2.value="audio" It seems that all the API is reinventing SQL. Why not just use SQL in the first place? </blockquote><div> I take it you are talking about the query language..? I'm not really an expert on SQL so stop me if I'm rambling. Is it possible to do proximity searches ("foo" appears within 6 words of "bar"), fuzzy searches (search for words that looks like "foobar"), weighted words. Also a design goal is to have the language easily extensible, and I don't really connect that with SQL (without ending up with something that isn't SQL anyway). </div> Cheers, Mikkel </div>