If your DBMS doesn't (or isn't configured to) give a shit, the results you see will be non-deterministic (I.e. "UB" - undefined behaviour).
The person and MAX(date) columns will be correct, but the fur_score column could contain any of the fur_score values for that person - not necessarily the one associated with the row that the value for MAX(date) came from. You might get something like:
person fur_score MAX(date)
steve 0.41 2023-10-02
james 0.5 2023-10-05
steph 0.6 2023-10-09
Ret the Folf /
npub136…xkh6w
2025-04-16 21:18:11
in reply to nevent1q…04f8
Author Public Key
npub136mqky5kqr4jxtvulh2dq8egal2408t3tf3rptq0ah0ydufsfx3qzxkh6wSeen on
wss://relay.mostr.pubPublished at
2025-04-16 21:18:11Event JSON
{
"id": "972015a28188ffad4fc9c0215f681153a75a553f162424fd8ab7de51387b89e8",
"pubkey": "8eb60b129600eb232d9cfdd4d01f28efd5579d715a6230ac0fedde46f13049a2",
"created_at": 1744838291,
"kind": 1,
"tags": [
[
"e",
"511fa2885dbc1de5bff2dce6d56ba8c2d8cb5331daaf2383e0faa43782d5379c",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://furry.engineer/users/ret/statuses/114349722246995179",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.mostr.pub"
]
],
"content": "If your DBMS doesn't (or isn't configured to) give a shit, the results you see will be non-deterministic (I.e. \"UB\" - undefined behaviour). \n\nThe person and MAX(date) columns will be correct, but the fur_score column could contain any of the fur_score values for that person - not necessarily the one associated with the row that the value for MAX(date) came from. You might get something like:\n\nperson fur_score MAX(date)\nsteve 0.41 2023-10-02\njames 0.5 2023-10-05\nsteph 0.6 2023-10-09\n",
"sig": "130a3ac0f9920bbe8ec5d3f349eee7358faf2a584a8ebab2330b6695f1c3f50625b3728f194a731ecbfc78eb1f92c3ba3d1919453285b5586dd939fa85b223b3"
}