Created attachment 117957 [details]
Overview given by Base's query wizard
I have created a spreadsheet to make it easier to choose which one of specific items to buy. I figured I'd use an SQL database to query the colums for some specific info.
Since 2 of the columns got a newline, the query created by the wizard is syntax violation. Once the newlines are removed, it works perfectly.
Created attachment 117958 [details]
Created attachment 117959 [details]
The error details and the SQL the wizard created
@Jouni : if I have understood you correctly, you are expecting Base to deal with line feed characters in your field names. I don't know of any database program that allows that to happen (unless maybe Access does ?). The line feeds for your column headers are purely for presentation / display purposes when the sheet is opened in Calc.
At the moment, I fail to understand what the problem is, or why you think that Base should support such line feed characters in its field names.
Did this, for example, work in previous versions of LibreOffice ? If so, then at least we could confirm that this is a regression, but if not, then theoretically an enhancement request. In the latter case, how should Base know to ignore a line feed character in field name, and what would it substitute that character with (space, underscore, hyphen, delete ?) but not in the data corresponding to a tuple ?
Seems like a very non-trivial coding request to me for little benefit to the user, especially when the workaround is simple, i.e. don't put line feeds in your column headers if you want to then import that spreadsheet into Base.
Base could auto-convert newlines to something else, such as a space, and notify the user. The big deal is you have to completely re-do whatever you entered in the wizard if you didn't know Base can't handle some character[s] you had to use in Calc, for instance.
Well, whatever, added as enhancement request.
5.0.4 RC1 (22.214.171.124) x64 tested, the newlines are automatically replaced with nothing, uglily concatenating the lines but at least it works just fine. It takes pretty long loading the result, though, on AMD A4-5000 APU which has broken/incomplete OpenCL support regardless of driver version (I'm using very latest betas as they come, but I get no notifications and don't realize to check often).