Bug 128184

Summary: Crash in: connectivity::OSQLParser::predicateTree : crash running query with parameter.
Product: LibreOffice Reporter: herman.viaene
Component: BaseAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: serval2412, xiscofauli
Priority: medium    
Version: 6.3.0.4 release   
Hardware: All   
OS: All   
Whiteboard:
Crash report or crash signature: ["connectivity::OSQLParser::predicateTree"] Regression By:

Description herman.viaene 2019-10-16 14:16:47 UTC
This bug was filed from the crash reporting server and is br-4f197ce2-3a35-448f-93ee-26b6890d280b.
=========================================
Setting up query with four tables (of which 2 times the same) and define a parameter on one field (of a table used once in the query).
Query seems OK, no syntax problems, but running it crashes after entering a valid value for the parameter.
When I reopen the query in edit mode, it is completely garbled : unwanted table added, calculated field split up in its components. e.a.
Comment 1 Julien Nabet 2019-10-16 16:45:13 UTC
Which type of database do you use? hsqldb embedded, Firebird embedded, Mysql, ...

Would it be possible you attach an example file to the bugtracker after sanitizing it? (see https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission)

Also, could you give a try to 6.3.2?
Comment 2 herman.viaene 2019-10-17 15:03:46 UTC
I will try yo make an example file, but in the mean time:
1. its Firebird embedded
2. the error occurs when the parameter applies to a text field AND the input given contains a "space" character. No problems with numeric input or text input without spaces.
Comment 3 QA Administrators 2019-10-18 02:41:59 UTC Comment hidden (obsolete)
Comment 4 Xisco FaulĂ­ 2019-10-18 11:36:50 UTC
I think this issue is fixed in the latest version.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 5 Alex Thurgood 2019-10-18 12:01:33 UTC
Pretty certain that the space in a character string as a parameter in a query has already been reported in LO bugzilla.
Comment 6 herman.viaene 2019-10-18 14:12:24 UTC
I cannot reproduce the error in version 6.3.2. There the query works OK.
Comment 7 Julien Nabet 2019-10-18 14:13:08 UTC
Thank you Herman for your feedback, let's put this one to WFM then.