An idea to help organize your music with extra metadata using a SQL Server Database. This repository searches through a folder and gathers metadata already in mp3 files to add to a database
2
stars
1
forks
source link
Subtable Data Needs Salt To Prevent Matching Conflicts #7
The subtables use an Identity column as their key, so during generation that value is not available until the entry is added. Currently, the only other column we have is the name or description of the data in the subtables. If 2 albums or 2 artists have the same name, we would map both to the same data in the subtables. This is undesirable. More data is needed to differentiate between this kind of data specifically in the Artist and Album tables.
Artist - Just needs more specific data about the artist to differentiate them from other artists
Album - Consider adding a reference to the primary artist associated with the album directly in the table
Consider adding a unique constraint to everything other than the identity column in these tables
The subtables use an Identity column as their key, so during generation that value is not available until the entry is added. Currently, the only other column we have is the name or description of the data in the subtables. If 2 albums or 2 artists have the same name, we would map both to the same data in the subtables. This is undesirable. More data is needed to differentiate between this kind of data specifically in the
ArtistandAlbumtables.Artist- Just needs more specific data about the artist to differentiate them from other artistsAlbum- Consider adding a reference to the primary artist associated with the album directly in the tableConsider adding a unique constraint to everything other than the identity column in these tables
See related: https://github.com/JeffreyGaydos/music-database-generator/issues/5