Bug 147669 - Calc - MATCH gives wrong result with an inline array
Summary: Calc - MATCH gives wrong result with an inline array
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.3.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-26 10:01 UTC by David Lynch
Modified: 2024-05-09 03:16 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Exhibits bug 147669 (12.19 KB, application/vnd.oasis.opendocument.spreadsheet)
2022-02-26 10:03 UTC, David Lynch
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Lynch 2022-02-26 10:01:52 UTC
Description:
See attached.
=MATCH("2",{2;3},0) gives #N/A (incorrect)
=MATCH("2",C4:D4,0) gives 1 (correct) if C4=2 and D4=3


Steps to Reproduce:
See attached

Actual Results:
See attached

Expected Results:
See attached


Reproducible: Always


User Profile Reset: No



Additional Info:
I need the first parameter to MATCH be a string because in my application it is a regular expression.
Version: 7.3.0.3 (x64) / LibreOffice Community
Build ID: 0f246aa12d0eee4a0f7adcefbf7c878fc2238db3
CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-GB (en_GB); UI: en-GB
Calc: threaded
Comment 1 David Lynch 2022-02-26 10:03:36 UTC
Created attachment 178556 [details]
Exhibits bug 147669
Comment 2 Mike Kaganski 2022-05-08 09:51:50 UTC
Note also, that it works with

=MATCH("2";{"2"|"3"};0)

=> it gives the expected 1.

MATCH with MatchType = 0 is defined in ODFF 1.3 [1] differently compared to MatchType = 1 and MatchType = -1; for the two latter, there's explicit "If Search is of type Text and the value found is of type Number, the #N/A Error is returned", while for the former, no such clause exists, implying that the return value of 1 is really expected here.

[1] https://docs.oasis-open.org/office/OpenDocument/v1.3/OpenDocument-v1.3-part4-formula.html#MATCH
Comment 3 QA Administrators 2024-05-09 03:16:36 UTC
Dear David Lynch,

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://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug