Issue 71000 - Functions are never case-sensitive, wording of application setting is misleading
Summary: Functions are never case-sensitive, wording of application setting is misleading
Alias: None
Product: Calc
Classification: Application
Component: programming (show other issues)
Version: OOo 2.0.4
Hardware: All All
: P3 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: oooqa
Depends on:
Reported: 2006-10-30 12:49 UTC by drking
Modified: 2017-05-20 11:00 UTC (History)
3 users (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description drking 2006-10-30 12:49:41 UTC
1    BC
2    bc
3    =IF(A1=A2;"matches";"doesn't match")
4    =IF(COUNTIF(A1;A2);"matches";"doesn't match")

with regexp enabled. Both formulae should surely produce the same result, to
match only when case sensitivity is not enabled. Only the A1=A2 test considers
case and works correctly; the regexp in COUNTIF always matches even if case
sensitivity is enabled.

Note Issues 69909 and 15339, both involving work on regexp; this issue is
different, specific and unreported.
Comment 1 dridgway 2007-01-02 05:31:34 UTC
Confirming 2.1 OSX. Not specific to regexp, adjusting summary. There are several
functions which are documented with specific case sensitivity, irrespective of
global case sensitivity option (EXACT, SEARCH, FIND, maybe others), but COUNTIF
isn't one of them, so there's definitely a defect, either in the implementation
or documentation.
Comment 2 drking 2007-01-02 07:05:13 UTC
Thank you.

Please note that SUMIF is also at fault.

Comment 3 ooo 2007-01-08 13:00:41 UTC
Grabbing issue.
Comment 4 ooo 2007-01-08 13:01:13 UTC
Comment 5 ooo 2007-04-04 15:20:48 UTC
Seems I grabbed this issue in a moment of blackout. Rethinking this it turns out
that no function considers the case sensitivity option. The option was
introduced for compatibility with older versions of StarCalc that always were
case sensitive with the '=' and '<>' operators and to create a compatibility
mode with Excel. Note that the functions that are documented to be
case-sensitive are always case-sensitive, regardless of the application setting.

So, actually this is a bug in the wording of the dialog and the online-help.
Comment 6 drking 2007-04-04 16:10:34 UTC
Oh, yuk!

So the options dialog presumably needs separating into check boxes that work 
with =A1=A2 and those that work with COUNTIF, SUMIF,.. with some explanation on 
the dialog

Comment 7 Martin Hollmichel 2007-11-09 16:51:55 UTC
change target from 2.x to 3.x according to
Comment 8 huw 2007-12-11 13:39:00 UTC
Is this in any way related to the "Case sensitive" option in a filter? That 
works correctly (even if using regex), except when used with the "No 
duplication" option, where it is ignored.
Comment 9 ooo 2007-12-11 16:56:34 UTC
@huw: Should not be related to the 'Case sensitive' option in filters. I also
don't see where "except when used with the 'No duplication' option, where it is
ignored" applies. If I select 'Case sensitive' and 'No duplication' in a filter
I get unique entries. Anyway, if there's anything wrong with that it would be a
different issue.
Comment 10 Marcus 2017-05-20 11:00:59 UTC
Reset assigne to the default "".