History:Next Generation Schema/History: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(link to ToSchemaOrNotToSchema (Imported from MoinMoin))
(correct link (Imported from MoinMoin))
Line 17: Line 17:
* [[Advanced Entity|AdvancedEntity]] (for creating new entity types like the ones we already have (artists, albums, tracks, URLs))
* [[Advanced Entity|AdvancedEntity]] (for creating new entity types like the ones we already have (artists, albums, tracks, URLs))
* [[Getting Rid Of Featuring Artist Style|GettingRidOfFeaturingArtistStyle]] (for support of multiple artists of one track/album or alternatives)
* [[Getting Rid Of Featuring Artist Style|GettingRidOfFeaturingArtistStyle]] (for support of multiple artists of one track/album or alternatives)
* [[Disentangle Interfaces From Schema|DisentangleInterfacesFromSchema]] asks what a schema change can and should do, and more importantly what it should not do.
* [[To Schema Or Not To Schema|ToSchemaOrNotToSchema]] asks the quesiton wheter we need a schema change at all.


[[Category:To Be Reviewed]] [[Category:Development]]
[[Category:To Be Reviewed]] [[Category:Development]]

Revision as of 12:01, 16 November 2005

This is a process working towards a greater release covering a lot of database schema changes and the connected interface and client changes. (started in October 2005)

The changes are related to album groups, track groups, multiple artists and many more issues and produce a lot n:n tables.

At the moment we are in the planing phase so this is FutureWork.

Previous documents addressing those changes are (some only of historical interest):

The current rework is split into: