Dan Boehm

Congratulations to @geigerzaehler for what was obviously quite a lot of work for PR #527. As I understand it, this laid the foundation for multi-value tags, specifically adding support for...

To clarify a bit about what I think @pprkut was talking about, MusicBrainz does support multiple artists in its schema. It also provides access to that through the API. Here...

> That is, it would be great if code could refer to item.artist and get a single string even if there's another route to get the full list of artists....

These are good points. Unfortunately, that means we have to do this the standard way, which means implement new tables, which I was really hoping to avoid, because it really...

Perhaps we might be able to get away with not implementing lists with a few of the fixed fields that we know doesn't need this functionality. Dates for instance? Or...

> I think creating one-off tables for a few fields where lists are important could be messier in the long run! I'm certain that, in the future, we'll think of...

> As for the discussion that’s unfolding I just would like to point out that it’s probably best to delay writing code I agree about the code-writing part. It's best...

I know it has been awhile, but I've been looking into this issue in my spare time. Based on what I've learned about python's sqlite3 package, relational database design, and...

> I'm a little confused about your comment about conversion to strings. I am pretty sure we don't do this—can you explain why you think we're converting all values to...

@geigerzaehler I looked into both of the possibilities given in the wiki. One of them would result in the same problems we are currently having, because you have to define...