Kenneth Wagner wrote:
> 1. The resultset display runs off the screen to
> the right.
I guess there are char/varchar columns with many (possible) characters.
> 2. The column width is 2-4 times as long as the
> data displayed.
Just accident. If you have more data in the record then the column will still display the same, just contain more data.
> 3. Adjust the column widths so all display nicely
> on the screen. Little or no empty space.
> 4. Re-execute the query.
> 5. The resultset display is now spread out again.
This is something we already have discussed. It is difficult to pick a useful default column width, so we based this decision on the datatype. However often (particulary with text) the data is much less than what is specified in the column type. So the set column width appears much wider than necessary. However it could well be that some records contain much more data and without reading all records we cannot decide. So it is not an option to bind the automatic column width to the actual data.
What we have in mind though, is to keep the column width a user has set for a specific column or even a specifc datatype and use this value for all further result sets. This feature won't be here before QB 2.0, though.
> Must be a bug because the table editor remembers
> its screen column widths after the table editor
> window is resized and the columns have their
> display widths changed.
This is something totally different, because the table editor has not to choose its column width base on (variable) data types.
> So frustrating to re-set the column widths after
> each execute.
I know, but that's how it works right now.
> How to work around? Fix?
Other than using datatypes with less characters? No, not that I'm aware of, sorry.
Mike
Mike Lischke, MySQL Developer Tools
Oracle Corporation
MySQL Workbench on Github:
https://github.com/mysql/mysql-workbench
On Twitter:
https://twitter.com/MySQLWorkbench
On Slack: mysqlcommunity.slack.com (#workbench)
Report bugs to
http://bugs.mysql.com
MySQL documentation can be found here:
http://dev.mysql.com/doc/refman/8.0/en/