From 0a985fdfb4add8eeb5d2bb73233a78057e690745 Mon Sep 17 00:00:00 2001 From: "Arav K." Date: Sun, 8 Sep 2024 14:14:37 +0200 Subject: [PATCH] [doc/reference/config] Re-write explanation for 'overwrite_null' See: --- docs/reference/config.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/reference/config.rst b/docs/reference/config.rst index 60b641082..234185e79 100644 --- a/docs/reference/config.rst +++ b/docs/reference/config.rst @@ -281,11 +281,11 @@ That is, if this option is turned on, then ``year`` will always equal overwrite_null ~~~~~~~~~~~~~~ -In some situations, data for a particular field is not available, and it ends up being -set to an empty value (an empty string). To allow such fields to be overwritten once -the appropriate data does become available (e.g. by a re-import or a manual update), -the name of the metadata field can be added to the list `album` (for albums) or `track` -(for tracks). For example:: +This confusingly-named option indicates which fields have meaningful `null` values. If +an album or track field is in the corresponding list, then an existing value for this +field in an item in the database can be overwritten with `null`. By default, however, +`null` is interpreted as information about the field being unavailable, so it would not +overwrite existing values. For example:: overwrite_null: album: ["albumid"]