A library list and a made-up folder disagree with upstream #51
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two collections come back in a different order from upstream's.
/System/Info/Storage— the libraries:/Library/MediaFolders— the synthesized Playlists folder carries noDateCreatedhere, where upstream sends the zero date:DateCreated0001-01-01T00:00:00.0000000ZThe three real libraries agree on their dates exactly. Absent and a value are
different answers to a client, and the zero date is what upstream gives a folder
it made up rather than read.
Both measured against a production database with three libraries; the reference
library has too few for an ordering to disagree.
Both halves fixed, and the second turned out to be far wider than this issue
said.
The library list is ordered by name. Upstream builds it from a listing of
the directory its views live in — one directory per library, named after it —
so the names are what order them. This server was ordering by creation date,
which put
ShowsbeforeMusicbecause the shows library is older.The dateless row was not one folder.
DateCreatedis read into a type thatcannot be absent, so upstream answers
0001-01-01T00:00:00.0000000Zfor everyrow storing nothing, and this server omitted the field for all of them —
1032 rows of the measured library, not the one Playlists folder this issue
named:
Confirmed against upstream live for studios, music genres and the playlists
folder before changing anything — absent against a value is a difference a
client can see, and every by-name listing carried it.
All three now agree with a running upstream over a production database.