MySQL Bugs: #57328: Request: Ability to 'freeze' column(s) in Edit Table view

Bug #57328	Request: Ability to 'freeze' column(s) in Edit Table view
Submitted:	7 Oct 2010 23:48	Modified:	22 Aug 2014 15:37
Reporter:	Doc Billingsley	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S4 (Feature request)
Version:	5.2 CE	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	Edit Table, feature request, freeze column

Description:
Whenever I edit tables that have a lot of columns, I often lose track of which row I am working on. It would be very helpful if we could 'freeze' columns, even if just the first (id) column (though it would be much more useful if we could also select any given number of colums to freeze), similar to the functionality of freezing panes in a spreadsheet program.  This way, I'd be able to freeze my ID and, in my case, 'Book title' columns so they'd always be visible on the left-hand side as I'm scrolling through and adding data to the other columns. 

How to repeat:
This is a feature request

Suggested fix:
This is a feature request

Thank you for the feature request.

Has anything been done about this ? that would be very useful to freeze some columns on the left side when editing tables when there are a great number of columns, thanks and regards.

Posted by developer:
 
Added storage of resultset column widths

The bug seems to have reappeared (http://stackoverflow.com/q/24316895/395857). I use MySQL Workbench 6.1.6.11834 on Windows 7 SP1 x64 Ultimate.

This is driving me nuts. I just switched over to WorkBench and it was all going great until I hit this issue.

I cannot imagine any DBA who can tolerate this.

Every column is too narrow so I had to run the query, grab the mouse, expand every columns I am interested in, inspect the results, re-run the query as needed and then resize everything again.

Sequel Pro plays is more intelligent about it and I realise I have never had to resize columns there.

I am on OS X using v 6.1.7.11891 b1788

I appreciate if this issue could be fixed as soon as possible.

Thanks.

The original request (which seems to be unrelated to the comments that come in later) will not be implemented as it's a significant effort for the few use cases it has. OTOH, we now have a form editor which should make editing records easier. Feature request from Bug #73377 is also similar and could be made to display the primary key of the record.

As for the unrelated comments, WB 6.2 has autosizing and saving of column widths implemented.