Complete date-ordered orderings #29

Merged
Aaron merged 1 commits from electricdusk/pics:assets-complete-ordering into master 2022-11-22 21:09:11 +01:00
Member

Bug as reported by Yorick: When two Assets have the same capture
date, a bug occurs in the interface where the user gets stuck in
a loop when moving to the next image.

This patch uses the primary key as a fallback when ordering the
images by capture date. This way, the asset ordering is complete
and it should resolve the bug.

Bug as reported by Yorick: When two Assets have the same capture date, a bug occurs in the interface where the user gets stuck in a loop when moving to the next image. This patch uses the primary key as a fallback when ordering the images by capture date. This way, the asset ordering is complete and it should resolve the bug.
electricdusk added 1 commit 2022-11-22 12:03:18 +01:00
Bug as reported by Yorick: When two Assets have the same capture
date, a bug occurs in the interface where the user gets stuck in
a loop when moving to the next image.

This patch uses the primary key as a fallback when ordering the
images by capture date.  This way, the asset ordering is complete
and it should resolve the bug.
Author
Member

Cc @Aaron

Cc @Aaron
Aaron approved these changes 2022-11-22 20:41:39 +01:00
Aaron left a comment
Member

Thanks, this is a nice fix for the bug. Also, I wasn't familiar with this tuple SQL syntax, so I learned something new as well :-)

Thanks, this is a nice fix for the bug. Also, I wasn't familiar with this tuple SQL syntax, so I learned something new as well :-)
Aaron merged commit 7d82a4a924 into master 2022-11-22 21:09:11 +01:00
electricdusk deleted branch assets-complete-ordering 2023-01-05 13:58:42 +01:00
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Public/pics#29
No description provided.