• ck_@discuss.tchncs.de
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    I think the most_recent is to power the unique index constraint. This “powers” the whole thing.

    That much is clear, the question is: why is it needed at all? The sort key has the same uniqueness constraint, so there cannot be two entries with the same sort key value. So under which circumstances does the highest sort key value not reject the most_recent transaction?

    • towerful@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      I guess separation of concerns? One is for the system, one is for display?

      A unique Boolean is easier to query than sorting and limiting?

      Maybe you don’t ever need the ability to display a history, but you still want the history (instead of just making the transaction_id unique constrained)… so you just drop the sort_order column?

      I understand what you are saying.
      Maybe that’s just how they went about it. Originally planning on using created_at to do the ordering, then later realising that a customisable sort_order is required so they can make things make sense without having to fudge timestamps.