PlaylistSongs table: Difference between revisions
Jump to navigation
Jump to search
m ({{DatabaseTablesList}}) |
({{DatabaseTablesList}} and removed "need more info" since there's a description for each field) |
||
| Line 30: | Line 30: | ||
| Entries in a database are unordered, so the playlist order must be made explicit. All numbers must be filled in, starting with zero. | | Entries in a database are unordered, so the playlist order must be made explicit. All numbers must be filled in, starting with zero. | ||
|} | |} | ||
Latest revision as of 16:02, 11 April 2024
- [Database Structure]
- Albums
- Artists
- ArtistsAlbums
- ArtistsSongs
- Covers
- DBInfo
- DeviceFilters
- DeviceTracks
- Devices
- Downloads
- Filters
- Folders
- FoldersHier
- Genres
- GenresSongs
- LastTreePath
- Lists
- ListsSongs
- Medias
- OrganizeRules
- PathProcessing
- Pinned
- Played
- PlaylistSongs
- Playlists
- PodcastDirs
- PodcastEpisodes
- Podcasts
- Radio
- RemoteClients
- Songs
- SynchAlbum
- SynchArtist
- SynchLocation
- SynchPlaylist
- SynchPodcast
- URLRequestCache
The PlaylistSongs table can be used for retrieving song IDs from a given playlist. Every song in every playlist resides in this table.
Fields
| Name | Value Type | Possible Values | Description |
|---|---|---|---|
| IDSong | INTEGER | Primary Key | Each playlist entry has a unique identifier |
| IDPlaylist | INTEGER | Primary key from the Playlists table. | The playlist that this entry's song resides in. |
| IDPlaylistSong | INTEGER | Primary key from the Songs table. | The song to be used for this entry in the given playlist. |
| SongOrder | INTEGER | Zero-based index, ordering the entry in the playlist. | Entries in a database are unordered, so the playlist order must be made explicit. All numbers must be filled in, starting with zero. |
