fix(playlists): keep imported playlist track order (#482)

Playlist tracks were read newest-first (added_at DESC, rowid DESC),
so a batch import - inserted in playlist order with one timestamp -
came back reversed, and the in-memory prepend matched that. Playlists
now use insertion order: snapshot reads ASC, single adds append, and
batch adds append in order. Existing rows were already stored in
playlist order, so old libraries display correctly without migration.
The preview-cover query follows the first visible track.
This commit is contained in:
zarzet
2026-07-14 09:09:53 +07:00
parent 9a205987ee
commit a287d6b815
2 changed files with 8 additions and 4 deletions
@@ -269,7 +269,10 @@ class LibraryCollectionsDatabase {
);
final playlistTrackRows = await db.query(
_tablePlaylistTracks,
orderBy: 'playlist_id ASC, added_at DESC, rowid DESC',
// Playlists keep playlist order: batch imports insert rows in playlist
// order and later additions append, so insertion order IS the order
// (unlike wishlist/loved, which show newest first).
orderBy: 'playlist_id ASC, added_at ASC, rowid ASC',
);
final favoriteArtistRows = await db.query(
_tableFavoriteArtists,
@@ -348,7 +351,7 @@ class LibraryCollectionsDatabase {
SELECT inner_tracks.rowid
FROM $_tablePlaylistTracks inner_tracks
WHERE inner_tracks.playlist_id = outer_tracks.playlist_id
ORDER BY inner_tracks.added_at DESC, inner_tracks.rowid DESC
ORDER BY inner_tracks.added_at ASC, inner_tracks.rowid ASC
LIMIT 1
)
''', playlistIdsNeedingPreview);