StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PODatabase design for dance-event tracklist storing
primarykey
Id
9664571
data
AcceptedAnswerId
9666767
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-03-12T09:32:18.047
FavoriteCount
0
LastActivityDate
2012-03-12T12:11:42.223
LastEditDate
LastEditorUserId
0
OwnerUserId
312700
ParentId
0
PostTypeId
1
Score
0
ViewCount
137
LastEditorDisplayName
text
Body
I am writing a simple interface in Python for a simple database. The database is a simple database which stores which certain tracks where played at which event and by which artist. The interface in Python isn't yet the problem, though the design of the database is. I've come up with the following thing: <pre><code>--- EVENTS --- CREATE TABLE events ( id INTEGER PRIMARY KEY autoincrement, event_name TEXT NOT NULL, event_date TEXT NOT NULL, <list of tracklist-ids - foreign key?> ); --- TRACKLISTS --- CREATE TABLE tracklists ( id INTEGER PRIMARY KEY autoincrement, artist TEXT NOT NULL, <list of track-ids - foreign key?> ); --- TRACKS --- CREATE TABLE tracks ( id INTEGER PRIMARY KEY autoincrement, trackartist TEXT NOT NULL, trackname TEXT NOT NULL, timesplayed INTEGER NOT NULL, ); </code></pre> It just doesn't feel logical for me, I need way to many operations to get some simple things out of the databases, few examples: <ul> <li>Get a list of songs (tracks) played by artist A in the years 2006 till 2009: would require looping through the 'tracklists' table to get every tracklistid of artist A, then look it up in the 'events' table (which is already a pain, how to store a list?)</li> <li>Lookup which artist played track A most of the times: loop through the whole 'tracklists ' table and get some sort of counter which looks for the trackid of track A</li> </ul> It might become a bit confusing because I'm talking about a lot of different things but to me it seems my database can be designed much better or should I use some kind of other approach to tackle this program database-wise? I'm looking for a basic start-off or hints/tips to get this database much more efficient and better. I know that not every lookup can be fast but to me this does not seem very efficient. Also, is there a better way of storing list into a SQL-database without having them to store them into strings?
Tags
<python><database><sqlite><database-design>
Title
Database design for dance-event tracklist storing
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USwvd
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.