-
-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sequential updates not used when multi-column index is present #360
Comments
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, it's not necessarily connected to the DB yet and nor should it be (in some cases). :) I think the best bet would just to document the feature :D I didn't realise it snuck through undocumented! Would you be interested in doing up a PR for this? :) |
Thanks for a fast response @brendon I share your sentiment on this. I think we can: a) Try to make the gem smarter, add complexity, possibly introduce bugs (you're right, been there too 😄) The latter is a clear winner for me, I'll look into it and open a PR. |
Thanks @janklimo :) That's very much appreciated. |
Hi @janklimo, I can't remember, did you ever put forward a documentation update? :) |
Did this ever get fixed? I'm seeing the same issue now 😞 |
As far as I know it wasn’t. |
Closing due to inactivity. |
Given the following index (Postgres):
sequential updates will not be used (and reordering always fail) unless explicitly specified:
One way to fix this would be to scan all indexes of the target table in
SequentialUpdatesMethodDefiner
and see if any of them include position. Another way is just to mention this in the docs. Opening a conversation first.The text was updated successfully, but these errors were encountered: