Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

updated song metadata handling #63

Open
avuserow opened this issue Dec 30, 2010 · 0 comments
Open

updated song metadata handling #63

avuserow opened this issue Dec 30, 2010 · 0 comments

Comments

@avuserow
Copy link
Owner

We should store as many tags from a song as possible.

SQL can look something like:

create table songs(song_id INTEGER PRIMARY KEY, path STRING);
create table metadata(song_id INTEGER, key STRING, value STRING, searchvalue STRING, song_id REFERENCES songs(song_id));

This assumes all tags are strings. For the ones that are not, we can either add an intvalue column, or just store them as strings. Or we can store them as a blob somehow.

The searchvalue column can be a non-unicode, trimmed, lowercased, etc version of the value. This is for ease of searching.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant