Created attachment 74481 [details]
Open the query and try to chga the with of the field "Name and Town"
In Base you could change the column-width of tables and of queries. Mostly the automatic values are unusable. So I have changed it with the context-menue or by dragging the header with the mouse.
When I change this in the tables it is saved in the *.odb-file. Opening the file later and the column has the same width when I have closed the table the last time.
When I change the width in a query it hasn't be saved in the *.odb-file. Opening the query again and the columns are set to "automatic" again - except the columns, which have been set manually by changing the columns in the table.
Created attachment 74482 [details]
Detailed description where to change column-width
On pc Debian x86-64 with master sources updated today, I reproduced the different buggy behaviours you described.
In console logs, I noticed these kinds of messages, I don't know if there's a link:
warn:connectivity.parse:5164:1:workdir/unxlngx6/YaccTarget/connectivity/source/parse/sqlbison.cxx:9272: connectivity::OSQLParser::RuleIDToRule cannot reverse-lookup rule. Reverse mapping incomplete? _nRule='398' yytname[_nRule]='opt_group_by_clause'
warn:connectivity.parse:5164:1:workdir/unxlngx6/YaccTarget/connectivity/source/parse/sqlbison.cxx:9272: connectivity::OSQLParser::RuleIDToRule cannot reverse-lookup rule. Reverse mapping incomplete? _nRule='400' yytname[_nRule]='opt_having_clause'
There are a lot more like these.
Lionel: put you in cc, it might interest you.
When a query is executed in direct SQL-Mode it isn't possible to set the width of a column, too. There is a permanent width, exactly the same for every column, which couldn't be controlled by the width of the fields in the table.
Could be, that this is another bug. Could also be, that this would be fixed, when it is possible to save the width of a column with a query.
Adding self to CC if not already on