Issue 118672 - The result of a standard filter is wrong in certain cases.
Summary: The result of a standard filter is wrong in certain cases.
Status: CONFIRMED
Alias: None
Product: Calc
Classification: Application
Component: ui (show other issues)
Version: OOo 3.2.1
Hardware: All All
: P5 (lowest) Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-07 16:10 UTC by Starxpert
Modified: 2020-07-27 12:09 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Allows to reproduce the bug by following above instructions. (7.84 KB, application/vnd.sun.xml.calc)
2011-12-07 16:10 UTC, Starxpert 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Starxpert 2011-12-07 16:10:58 UTC 
Created attachment 77064 [details]
Allows to reproduce the bug by following above instructions.

Make a standard filter with 2 criteria : 
- choose "Begins with" as condition for the first one
- choose "=" as condition for the second one

The result is the same than a filter using "Begins with" as first condition and "Contains" as second condition.


To reproduce the bug on the attached document, apply the following filter on the data range of the sheet "Feuille1" :

       Dummy2    Begins with    va
and    Dummy1    =              erreur

=> All lines that contain "erreur" are kept visible whereas only those which match exactly "erreur" should remain visible.


However, if the two criteria are inverted, the result is correct.
Comment 1 Terry Yang 2012-09-07 05:05:10 UTC 
Confirm at my side
Comment 2 Stephen Wise 2019-10-19 21:32:46 UTC 
Issue still present in 4.1.7.  When first criterion is "Begins with" and second is "<>" on same field, returns no results at all, but works correctly in the opposite order.  It's probably the same bug.
Comment 3 b. 2020-07-27 12:09:22 UTC 
LO an AOO often have similar / identical issues, 

this bug looks different, i couldn't repro OP or c#2 with LO calc 6.1.6.3 nor 7.1.0.0.a0+ today, 

maybe 'compare code' is a way to approach the problem ... ?