Bug 60539 - FILESAVE: Column-width of a Query couldn't be saved
Summary: FILESAVE: Column-width of a Query couldn't be saved
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Database-Queries
  Show dependency treegraph
 
Reported: 2013-02-09 11:35 UTC by Robert Großkopf
Modified: 2017-11-02 23:28 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Open the query and try to chga the with of the field "Name and Town" (3.98 KB, application/vnd.oasis.opendocument.base)
2013-02-09 11:35 UTC, Robert Großkopf
Details
Detailed description where to change column-width (47.83 KB, application/vnd.oasis.opendocument.text)
2013-02-09 11:37 UTC, Robert Großkopf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Großkopf 2013-02-09 11:35:38 UTC
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.
Comment 1 Robert Großkopf 2013-02-09 11:37:24 UTC
Created attachment 74482 [details]
Detailed description where to change column-width
Comment 2 Julien Nabet 2013-02-19 21:06:17 UTC
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.
Comment 3 Robert Großkopf 2013-02-25 20:14:06 UTC
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.
Comment 4 Alex Thurgood 2015-01-03 17:40:53 UTC Comment hidden (no-value)