Skip to content

Resolve "Inserting hundreds of rows all with the same before parameter causes subsequent inserts with the same before to slow"

Merge Request Checklist

  • changelog.md has been updated if required
  • New/updated Premium features are separated correctly in the premium folder
  • The latest Chrome and Firefox have been used to test any new frontend features
  • Documentation has been updated
  • Quality Standards are met
  • Performance: tables are still fast with 100k+ rows, 100+ field tables
  • The redoc API pages have been updated for any REST API changes
  • Our custom API docs are updated for changes to endpoints accessed via api tokens
  • The UI/UX has been updated following UI Style Guide

This MR try to improve a bit the situation creating the space for other 10000 rows between the new one inserted and the one selected as before_row. In this way we need to move all the rows with a lower value up once, and than we can insert up to 10000 rows before the same row without the need to update other rows' order values.

Not in this MR yet, but we can improve it even further decreasing the order of just the rows needed to create the space necessary for the new insert, instead of updating every row with a lower value and the same "decimal" part.

Closes #1083 (closed)

Edited by Davide Silvestri

Merge request reports