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 618829 - sum() - data table interaction
sum() - data table interaction
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Analytics
1.10.x
Other All
: Normal normal
: ---
Assigned To: Morten Welinder
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2010-05-17 01:22 UTC by Dave
Modified: 2010-05-18 00:42 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Gnumeric spreadsheet example of reported bug (2.44 KB, application/x-gnumeric)
2010-05-17 01:22 UTC, Dave 		Details

Description Dave 2010-05-17 01:22:55 UTC 
Created attachment 161195 [details]
Gnumeric spreadsheet example of reported bug

A data table calculated on a sum() doesn't always calculate correctly.

An example is attached. It shows three data tables; the first is calculated on a sum() of 24 cells and the result is correct. The second is calculated on a sum() of 25 cells and the table results are all the same (not correct.) The third is calculated on imsum() of the same 25 cells and is correct. Preliminary testing shows that if the sum() argument range is less than 24 cells the result will be correct, incorrect for 25 or greater. 

Gnumeric spreadsheet 1.10.1 running on Kubuntu 10.04 64 bit.

Also happens in Windows XP running Gnumeric 1.10.2
Comment 1 Andreas J. Guelzow 2010-05-17 03:46:17 UTC 
Thre are strange things happening. Just clicking on one of the cells in data table 2, changes the value in that cell (and possibly some other cells in that table). A recalculate returns the table to the original values. 

Please describe in detail how you created those tables.
Comment 2 Morten Welinder 2010-05-17 23:21:46 UTC 
Given the observed behaviour with 24 vs. 25, I would take a guess that
it's caused by the range caching:

	const int min_size = 25;
Comment 3 Morten Welinder 2010-05-18 00:42:34 UTC 
Probably fixed.

This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.