Is your feature request related to a problem? Please describe.
I would like to propose an improvement to the behavior of the table structure editor when pressing the Save button.
When I am modifying a table's structure (e.g., renaming a field or adding a new column) while scrolled down to a specific row—for example, row 75—pressing the Save button causes the entire table structure to refresh. The scroll position is completely lost, and I am taken back to the top of the field list, jumping back up every time. I then have to manually scroll down again to find the field I was working on. This becomes very frustrating when working with tables that have many columns.
Describe the solution you'd like
Expected behavior:
-
Preserve scroll position: After pressing Save, the table structure editor should remain exactly where it was—same row, same screen position—without jumping back to the top. The user should stay exactly on the field they were editing before saving.
-
Disable Save button after successful save: Once the save operation completes successfully, the Save button should become disabled (grayed out). It should only re-enable itself when the user makes the next modification to the table structure.
Describe alternatives you've considered
Manually scrolling down every single time I save a change. However, this is very slow, frustrating, and completely breaks the workflow when dealing with wide tables.
Additional context
This would greatly improve the workflow and the UX (user experience) when editing large table structures with many columns.
Thank you very much for your work and for keeping HeidiSQL such an amazing and reliable tool!
Is your feature request related to a problem? Please describe.
I would like to propose an improvement to the behavior of the table structure editor when pressing the Save button.
When I am modifying a table's structure (e.g., renaming a field or adding a new column) while scrolled down to a specific row—for example, row 75—pressing the Save button causes the entire table structure to refresh. The scroll position is completely lost, and I am taken back to the top of the field list, jumping back up every time. I then have to manually scroll down again to find the field I was working on. This becomes very frustrating when working with tables that have many columns.
Describe the solution you'd like
Expected behavior:
Preserve scroll position: After pressing Save, the table structure editor should remain exactly where it was—same row, same screen position—without jumping back to the top. The user should stay exactly on the field they were editing before saving.
Disable Save button after successful save: Once the save operation completes successfully, the Save button should become disabled (grayed out). It should only re-enable itself when the user makes the next modification to the table structure.
Describe alternatives you've considered
Manually scrolling down every single time I save a change. However, this is very slow, frustrating, and completely breaks the workflow when dealing with wide tables.
Additional context
This would greatly improve the workflow and the UX (user experience) when editing large table structures with many columns.
Thank you very much for your work and for keeping HeidiSQL such an amazing and reliable tool!