Created attachment 152611 [details] Try the query with a special character - won't work Open the attached database. open the query. Input 'e' as parameter. Query will work. Now input something like 'ä' or 'ö' or some special characters of your language. The query won't work. An error appears: *Malformed String This is the query: SELECT "ID", "Forename", "Surname" FROM "Table1" WHERE "ID" LIKE '%' || :search || '%' OR "Forename" LIKE '%' || :search || '%' OR "Surname" LIKE '%' || :search || '%' Field "ID" is INTEGER. Without searching "ID" it will work. LIKE works with every field-type (DATE, number-fields ...) if the content hasn't special characters. LIKE won't work with special characters in filed-types, which aren't fields for characters. Queries like the query above will work well in internal HSQLDB with special characters. My system: LO 6.2.5.2 on OpenSUSE 15 64bit rpm Linux
Confirmed with Version: 6.4.0.0.alpha0+ Build ID: 75d35ef8df1936dd93d5919b688abcaddb58bee8 CPU threads: 4; OS: Mac OS X 10.14.5; UI render: default; VCL: osx; Locale: fr-FR (fr_FR.UTF-8); UI-Language: en-US Calc: threaded
Have tested it with LO 6.3.0.2 now. The query doesn't work, but the errorcode has been changed: Error LO 6.3.0.2 → firebird_sdbc error: *arithmetic exception, numeric overflow, or string truncation *Cannot transliterate character between character sets caused by 'isc_dsql_fetch' Error LO 6.2.5.2 → firebird_sdbc error: *Malformed string caused by 'isc_dsql_fetch' Tested with OpenSUSE 15 64bit rpm Linux.
Dear Robert Großkopf, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug is still the same with LO 7.2.0.1 on OpenSUSE 15.2 64bit rpm Linux.
On pc Debian x86-64 with master sources updated today, I could reproduce this. It's indeed related to ID part since it works for the rest. I also noticed I could reproduce this too when using "Execute SQL statement" with or without "Run SQL command directly" enabled. Just wonder if it could be Firebird bug?
Looks like a character encoding issue. Try aligning the character set of the column / database and the one of the connection?
(In reply to Lionel Elie Mamane from comment #6) > Looks like a character encoding issue. Try aligning the character set of the > column / database and the one of the connection? SELECT a.RDB$CHARACTER_SET_NAME FROM RDB$DATABASE a returns UTF8 For column, I don't know what's the SQL command. Again, it works with Forename and Surname, just fails with ID. Perhaps converting UTF8 from ASCII part into INTEGER is ok but not UTF8 from outside ASCII?
(In reply to Julien Nabet from comment #7) > Again, it works with Forename and Surname, just fails with ID. > Perhaps converting UTF8 from ASCII part into INTEGER is ok but not UTF8 from > outside ASCII? Ah, I had missed that the problem is with an INTEGER variable. Try something like CAST("ID" AS VARCHAR CHARACTER SET utf8) LIKE '%'
(In reply to Lionel Elie Mamane from comment #8) > (In reply to Julien Nabet from comment #7) > > Again, it works with Forename and Surname, just fails with ID. > > Perhaps converting UTF8 from ASCII part into INTEGER is ok but not UTF8 from > > outside ASCII? > > Ah, I had missed that the problem is with an INTEGER variable. Try something > like > > CAST("ID" AS VARCHAR CHARACTER SET utf8) LIKE '%' This: SELECT "ID", "Forename", "Surname" FROM "Table1" WHERE CAST("ID" AS VARCHAR(10) CHARACTER SET utf8) LIKE '%é%' worked indeed in running direct SQL! VARCHAR(10) or whatever not just "VARCHAR". Putting it in the query adds quotes to UTF8 and so it becomes: SELECT "ID", "Forename", "Surname" FROM "Table1" WHERE CAST( "ID" AS VARCHAR ( 10 ) CHARACTER SET "UTF8" ) LIKE '%' || :search || '%' OR "Forename" LIKE '%' || :search || '%' OR "Surname" LIKE '%' || :search || '%' but it worked too.
IMHO perhaps we could consider this one as NOTABUG our NOTOURBUG? Robert/Lionel: what do you think?