Timeline for Storing a re-orderable list in a database
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 29, 2022 at 19:57 | comment | added | Rockiger | No, I am afraid not. | |
| Oct 28, 2022 at 16:51 | comment | added | enchance | @Rockiger were you able to find any more info on lexoranking? I also watched the video and it's hard to get a complete picture out of it. I can't seem to make heads of it. | |
| May 25, 2021 at 7:16 | comment | added | Rockiger | Not, that I know of. | |
| May 10, 2021 at 12:35 | comment | added | Moritz Friedrich | @Rockiger is there any text document about LexoRank available? I found that video incredibly hard to follow... | |
| May 2, 2020 at 12:15 | comment | added | Rockiger | Atlassian has an interesting video about their lexical ranking: youtu.be/OjQv9xMoFbg | |
| Mar 23, 2020 at 21:36 | comment | added | Antoine Jaussoin | You made my day! | |
| Mar 23, 2020 at 17:48 | history | edited | Alexander Bird | CC BY-SA 4.0 |
improved readability of the different sentences
|
| Mar 22, 2020 at 16:54 | comment | added | Alex Grin | I vote for this solution. And for those concerned about an edge case where we end up with too long strings (so long that their impact becomes noticeable from the point of memory and efficiency of Jira-scale DB?..) - you can always implement a background job that periodically (say, once a week) goes over these ranks and normalizes them. Provided that we're only interested in their relative values, not absolute. | |
| Apr 10, 2019 at 16:29 | comment | added | NSjonas | I was trying to come up with some way to do this by only updating a single record, and this answer explains the solution I was thinking up in my head very well. | |
| Apr 21, 2018 at 13:21 | history | answered | Alexander Bird | CC BY-SA 3.0 |