server: Set reply sorting to 'oldest'

[ggtylerr]

Checklist

• All new and existing tests are passing
• (If adding features:) I have added tests to cover my changes
• (If docs changes needed:) I have updated the documentation accordingly.
• I have added an entry to CHANGES.rst because this is a user-facing change or an important bugfix
• I have written proper commit message(s)
  

What changes does this Pull Request introduce?

Quick SQL patch to fix #1026

Why is this necessary?

Current reply sorting leads to confusion. See linked issue for details.

NOTE: I tested this briefly and it seems to be working (and of course unit tests pass) but I wasn't sure if the sorting option was actually going through. Hard to tell on the demo page. Will probably test tmrw over curl.

[ix5]

Hi, thank you for the quick patch! Left a few inline comments, mainly regarding the usage of comments.id for sorting which I'd prefer you switch to comments.created for consistency.

[ggtylerr]

Just confirmed the patch to be working now - you can see the results on my site. Here's the comment I showed as an example last time:

[ix5]

Thank you for addressing the feedback. Please squash your commits and give the resulting commit a more descriptive title/body, such as db: Set reply sorting to 'oldest'.

You also checked in an updated package-lock.json to your commit when you didn't mean to, please remove that as well.

[ggtylerr]

Fixed up as requested

[Kerumen]

@ix5 do you plan to merge and release this? Thanks 🙏🏻