After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 383400 - autofilter : equality comparisons between number and number as string
autofilter : equality comparisons between number and number as string
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: General
git master
Other All
: High normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2006-12-07 15:46 UTC by Valek Filippov
Modified: 2011-09-30 19:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
incorrect autofilter example (7.19 KB, application/octet-stream)
2006-12-07 15:48 UTC, Valek Filippov
Details

Description Valek Filippov 2006-12-07 15:46:26 UTC
Please describe the problem:
The autofilter seems to work incorrect in attached sheet
(can't reproduce with simple data).

Steps to reproduce:
1. Select autofilter in B4
2. Select 'Other'
3. Select 'equal' '6a' for 1st entry
4. Select 'OR'
5. Select 'equal' '95' for 2nd entry


Actual results:
Only the rows with '6a' are shown.

Expected results:
The rows with '6a' and the rows with '95' must be shown.

Does this happen every time?
It happens with this sheet. Quick attempts to check with numbers and numbers/strings mix didn't expose the problem.

Other information:
Comment 1 Valek Filippov 2006-12-07 15:48:39 UTC
Created attachment 77897 [details]
incorrect autofilter example

gnumeric version 1.7.5.
I tried to open this file in 1.6.1 with 'Incorect expression' dialogs and same (incorrect) behavior.
Comment 2 Morten Welinder 2006-12-07 16:11:01 UTC
Confirmed.  I also get this on load:

** (gnumeric:14089): WARNING **: too lazy to support nested unshared content for now.  We'll add it for 2.0

** (gnumeric:14089): WARNING **: Invalid attribute 'ValueType0', expected integer, received '6a'

** (gnumeric:14089): WARNING **: value_new_from_string problem.
Comment 3 Morten Welinder 2006-12-07 18:11:12 UTC
The problem is that...

xml-io.c and xml-sax-write.c interchanges the Value0 and ValueType0
attribute names.  xml-sax-read.c does not.

Hence the dom parser can read what it wrote and what the sax writer currently
writes.  But the sax reader cannot.
Comment 4 Jody Goldberg 2006-12-08 13:55:16 UTC
warnings are fixed.  There were a few problems.
The initial problem still exists.
Gnumeric compares the string '95' to the number 95 and sees them as unequal
Comment 5 Jody Goldberg 2007-06-09 02:05:10 UTC
Bump the priority to bring this up the queue.
Comment 6 Morten Welinder 2010-04-30 14:02:23 UTC
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.