2012-11-26, 21:40
I'm hoping one of the Dev's (or someone else) who looks after the music database could give me a little help.
My end goal is to add a "recently added singles" node for one of my machines which is only just used as a big jukebox.
First hurdle and i'm alittle stumped!
I'm trying to stop the re-ordering of idSong in the song table. Currently when you add a new song and the artist doesn't exist in the database it just adds the song to the end of the table using the next highest free idSong, but if you add a new song by an artist which already exists in the database the song id's will re-order all songs by that artist to use the next highest free idSongs. So at the mo there is no info to build a query because idSong changes and is not incremented just as new songs are added.
I've commented out x amount of stuff from musicdatabase.h & cpp and still can't find it!!
So if anyone can point in the right direction to stop the automatic re-ordering i'd be very grateful.
Thanks
My end goal is to add a "recently added singles" node for one of my machines which is only just used as a big jukebox.
First hurdle and i'm alittle stumped!
I'm trying to stop the re-ordering of idSong in the song table. Currently when you add a new song and the artist doesn't exist in the database it just adds the song to the end of the table using the next highest free idSong, but if you add a new song by an artist which already exists in the database the song id's will re-order all songs by that artist to use the next highest free idSongs. So at the mo there is no info to build a query because idSong changes and is not incremented just as new songs are added.
I've commented out x amount of stuff from musicdatabase.h & cpp and still can't find it!!
So if anyone can point in the right direction to stop the automatic re-ordering i'd be very grateful.
Thanks