Issue 103324 - Incorrect sorting algorithm in calc - VERY DANGEROUS BUG
Summary: Incorrect sorting algorithm in calc - VERY DANGEROUS BUG
Status: CLOSED DUPLICATE of issue 101690
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: OOo 3.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: spreadsheet
QA Contact: issues@sc
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-04 11:59 UTC by aespo
Modified: 2009-07-04 14:04 UTC (History)
3 users (show)

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


Attachments
Sorting this document by column A in ascending order produces wrong results (7.24 KB, application/vnd.oasis.opendocument.spreadsheet)
2009-07-04 12:02 UTC, aespo
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description aespo 2009-07-04 11:59:24 UTC
In some cases, when sorting data in calc, the single lines are not correctly kept together but instead 
elements belonging to one line end up in a different line after sorting. For example, in the following
case:
            columnA     columnB
Line 1       12             =A1*5
Line 2        4                   7
Line 3       57              =A3*5

after sorting by column A in ascending order, we obtain:

            columnA     columnB
Line 1        4                   7
Line 2       12              =A1*5
Line 3       57              =A3*5

Note that element B2 should correctly be =A2*5, but instead it is =A1*5.
This bug is very dangerous because it manipulates the data in the spreadsheet
in an an incorrect way, and the user may not notice that. This is extremely
dangerous especially if calc is used for structural or financial calculations.
Please correct this issue rapidly!
Comment 1 aespo 2009-07-04 12:02:48 UTC
Created attachment 63360 [details]
Sorting this document by column A in ascending order produces wrong results
Comment 2 Regina Henschel 2009-07-04 14:04:23 UTC
Yes, that is a known error. You can find the fix already in actual developer
snapshots. It will be available in the release OOo3.1.1.

*** This issue has been marked as a duplicate of 101690 ***
Comment 3 Regina Henschel 2009-07-04 14:04:58 UTC
closing duplicate