use created_at column for submission sorting #316
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Submissions are not sortable due to this query which expects the date to be in the data.
This issue is a regression from #306 where the date field is grabbed from the created_at column instead.
Result is that old submissions are sortable due to having a date property in data, but new entries do not.
Current query.
select * from form_submissions where form = 'tip_os' order by json_unquote(json_extract(data, '$."date"')) desc limit 100 offset 0This PR changes the query builder to use the
created_atcolumn for sortingThe new query will look like this:
select * from form_submissions where form = 'tip_os' order by created_at desc limit 100 offset 0