row field very large
But now, varchar fields are very large (more than 800 pixels large) when if I resize manually when do a refresh (F5), or restart heidisql, fields resize to the large value...
I tried to resintall the latest version, same thing.
I have the same problem.
If I change the value to 0, many columns are displayed very long. Also if the cells are empty in all rows.
If I change it to eg. 120 the "empty" columns are also Displayed so long.
I hope you unterstand my problem ;)
Isn't there any possibility to size the columns depanding on the data?
long data -> big field, no/short data -> small field.
I have been using HeidiSQL for about 3-4 months now and find it very easy to use. Great tool to have around.
One problem I have come across is the same as the users who have posted before me.
Was curious is it possible to have a setting which will either adapt to the field name size or/and field text, the lower of the two will be selected as the width?
This way if there is no data in the field it will just display the width of the field, and if there is data you will need to either hover over it to see the full size of the data.
Thanks.
Did you know
- the columns keep their resized state when refreshing data and
- that they now support autosizing on doubleclicking the border between two columns
in the latest builds? That's not exactly what you meant but probably it helps a bit.
I think what is most annoying here is that numeric columns take too much space. VirtualTree has an easy way to implement an autosized column depending on its datatype, how's that idea?
How about loading the table data, and then autosizing the columns then? Looking at whats smaller perhaps (?) or maybe just making it the width of the field names?
How about loading the table data, and then autosizing the columns then?
That implies that the complete data gets loaded at the beginning, which wouldn't be a good idea for my 55 gb laws tableOr did you mean that we only use the visible fields for autosizing? Would be odd I think.
How about loading the table data, and then autosizing the columns then?
That implies that the complete data gets loaded at the beginning, which wouldn't be a good idea for my 55 gb laws tableOr did you mean that we only use the visible fields for autosizing? Would be odd I think.
Well I guess that could be a problem. How about just making an option where the field names will determine the default width of the columns? This would be less problematic?
Related change: http://changes.heidisql.com/1712[/quote:a2a657e88c]
What does the value have to be set to for it to automatically do this? I can't seem to set it to 0?
Misunderstanding, sorry: r1712 didn't fullfill this request, it was just a related change, possibly of interest here.
I wouldn't say we should do this resizing automatically when the preference value of "Maximum column width..." is set to "0" or?
Well if "0" sets the default which is a reasonable size then I guess no need for it.
Can the column header sizes be saved, that way once you create a new table you can fix the widths of each column yourself and they will be saved? Maybe even have an option under "Columns" with "Save header size"? Or per column widths?
Try it out - nightly build of r1776 and following fixes should avoid some annoyance from now on.
seems to work for now ;)
Please login to leave a reply, or register at first.