Thanks for reporting this! We probably need to update this query to work with SQLite, in addition to MySQL.
Don't want to nag or rush but I'm curious when this will be fixed, as it's preventing a lot of functionality. Should I just switch to MySQL? I don't know what the difference is tbh and just did SQLite because it was easier lol.
Switching to MySQL would fix it in the short term, if that's easy for you to do! SQLite is definitely easier in many ways, since you don't need to set up / configure / maintain a MySQL database. But I plan to have this fixed within the next few weeks, and then we'll put out a bugfix release.
Of course, we'd also welcome pull requests from anyone who wants to fix this!