Description of problem: Please see https://redmine.darktable.org/issues/11353 for a detailed description. Darktable makes use of the limit functionality to return a row of interest, subject to a specified offset and order. When images are filtered by additional criteria (e.g., require the image ID be in another table for color ratings), the row returned is not the expected row as it does not obey the ordering requested. This issue appears to be fixed in SQLite 3.15.0, according to the release logs. Version-Release number of selected component (if applicable): 3.14.2 2016-09-12 18:50:49 29dbef... How reproducible: Reliably reproducible via sqlite3; see darktable's issue tracker for sample SQL. Steps to Reproduce: The same behavior can be replicated when interacting with the SQLite database file directly. For example, using the SQL dumped from sqlite3_expanded_sql as called from darktable, select id from main.images where (flags & 256) != 256 and (id in (select imgid from main.color_labels where color = 0)) order by datetime_taken, filename, version yields 1379, 1382, 1385 ... If one were to enter the darkroom view with the first image, select imgid from main.selected_images yields 1379. The offset as determined by dt_collection_image_offset in collection.c is 0, as expected. The following should yield the next image select id from main.images where (flags & 256) != 256 and (id in (select imgid from main.color_labels where color = 0)) order by datetime_taken, filename, version limit 1,1 but returns 360, not 1382. select id from main.images where (flags & 256) != 256 and (id in (select imgid from main.color_labels where color = 0)) order by datetime_taken, filename, version limit 1,-1 does yield 1382, 1385... Actual results: 360, not 1382 as image ID. Expected results: 1382 as image ID as next in sequence after 1379. Additional info: N/A
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.