Brendon Muir

Not since then. We still only lock in the `insert_at_position()` function. If you have any ideas for how to solve this I'd be more than grateful :D

It's probably more the implicit locks that come from updating large portions of the table at once (when shuffling positions etc...).

@vi-huynh, if you could do some more digging into this to figure out why, that would be helpful :) Keen to get this fixed :)

Thanks @ddengler for offering some more info :) I'm at a loss as to the cause but it's probably to do with table scan's locking rows even if they're not...

> Why are the requests not all ordered by the position column (either all 'asc' or 'desc')? It's not very surprising that there are deadlocks happening: if you want to...

Yea it's been an annoying problem for a long time. I don't have the time to rewrite anything, but am always happy to review PR's :D

Hi @dan98765, you're right about `sequential_updates` only being applied to some sections of the code. I think this was an oversight by the person who originally proposed that code. If...

Hi @janklimo, I've been in this position before, trying to sniff the default value of a column. It's actually more fraught than you'd expect as when a rails app boots,...

Thanks @janklimo :) That's very much appreciated.

Hi @janklimo, I can't remember, did you ever put forward a documentation update? :)