340
edits
OstDB DEV: Difference between revisions
Jump to navigation
Jump to search
m
→Approach 1
m (→Approach 1) |
m (→Approach 1) |
||
| Line 42: | Line 42: | ||
To Fix: | To Fix: | ||
* store type with song<->artist relations (i.e. composer, lyrics, singer, ...) | * store type with song<->artist relations (i.e. composer, lyrics, singer, ...) | ||
* rename some tables to make them more generic (ID3-Tags, Album?) | * rename some tables to make them more generic (ID3-Tags -> MetaData?, Album -> Collection?) | ||
* album<->song relation needs int trackno attribute | * album<->song relation needs int trackno attribute | ||
* maybe a song<->song relation "cover version of" ? | * maybe a song<->song relation "cover version of" ? | ||
| Line 49: | Line 49: | ||
* maybe try to unify typical data about a person in a new person table which can then be refered to by seiyu, artist and producer tables. (would also remove the need for a special artist<->seiyu relation) | * maybe try to unify typical data about a person in a new person table which can then be refered to by seiyu, artist and producer tables. (would also remove the need for a special artist<->seiyu relation) | ||
* multipilcities of released-by relation between audio file and audio group are wrong (switched) in diagram | * multipilcities of released-by relation between audio file and audio group are wrong (switched) in diagram | ||
* anime<->song relation with attributes (type: OP/ED, first-ep: eid) | |||
* ... | * ... | ||
Don't Fix?: | Don't Fix?: | ||
* we can't store very complex cases, but maybe we don't need to | * we can't store very complex cases, but maybe we don't need to | ||