Yeah, it *used* to be raw sql, but moved away, as it made it impossible to have a non-sql backend, or a backend that used a different dialect. For example, almost every db has different limit statements, so something that worked on sqlite wouldn’t work on mysql, which wouldn’t work on postgres, which *certainly* wouldn’t work on gdbm. And so forth.
Also, I eventually hope to be able to use playlists as a base library — for example, have a smart playlist like:
kids songs: comment !includes “explicit”
and then have a username and password (kids/kids), that uses that playlist as the “base” playlist. Then every other playlist would be a subselect on that one. It would be reasonably easy to do if the playlist was a simple where clause without sort info.
If that makes sense.