Reply to thread

Message

<blockquote data-quote="jameson_uk" data-source="post: 729007" data-attributes="member: 11220">Unlikely to be any changes as the really messy code that has built up over the years depends on it and I really don't fancy trying to rewrite the music view handler from scratch.That said the database is kind of like the that out of necessity&nbsp;&nbsp; The main issue is that you can have multiple values stored in artist/album artist/composer/genres.... tables.&nbsp;&nbsp; This multi-value / single field thing does not really agree with relational theory <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />&nbsp;&nbsp; Not sure what changes you would want to see?&nbsp;&nbsp; The Tracks table contains all your tracks and most of the info about those tracks.&nbsp;&nbsp; Multi-artist fields are stored in their own tables as unique values.&nbsp;&nbsp; This is meant to make it easier to get say an A-Z listing of artists because we need to store multiple values in one field in the tracks tables you have [code]| artist a | artist b |[/code] which makes that sort of query pretty difficult</blockquote>

[QUOTE="jameson_uk, post: 729007, member: 11220"] Unlikely to be any changes as the really messy code that has built up over the years depends on it and I really don't fancy trying to rewrite the music view handler from scratch. That said the database is kind of like the that out of necessity The main issue is that you can have multiple values stored in artist/album artist/composer/genres.... tables. This multi-value / single field thing does not really agree with relational theory ;) Not sure what changes you would want to see? The Tracks table contains all your tracks and most of the info about those tracks. Multi-artist fields are stored in their own tables as unique values. This is meant to make it easier to get say an A-Z listing of artists because we need to store multiple values in one field in the tracks tables you have [code]| artist a | artist b |[/code] which makes that sort of query pretty difficult [/QUOTE]

Verification