I’ve had beets complete processing a subsection of my library and afterwards took a look at the items table and ran a few queries against it. I noticed that the composer field (and presumably same applies to other fields) fails a IS NULL condition when there is no composer entry present in the record so the test becomes
composer != ""
Is there a reason that fields without values aren’t left in a null state when records are written to beets tables?
@adrian: Would my running an UPDATE query to set all ="" to NULL break anything within beets’ logic? Reason being I’ve previously written merge code to update my own database (which is based on my curated file tags) and bring in only data from records where the corresponding field of the associated record in my table is NULL. Rather than modify my code wherever a query references the NULL condition it’d be easier to set empty fields to NULL in the beets tables.