Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | |||||||||||
| 0038354 | |||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
| design defect | [Openbravo ERP] A. Platform | minor | always | 2018-04-12 15:56 | 2022-02-01 08:08 | ||||||
| Reporter | JONHM | View Status | public | ||||||||
| Assigned To | Triage Platform Base | ||||||||||
| Priority | high | Resolution | open | Fixed in Version | |||||||
| Status | acknowledged | Fix in branch | Fixed in SCM revision | ||||||||
| Projection | none | ETA | none | Target Version | |||||||
| OS | Any | Database | Any | Java version | |||||||
| OS Version | Database version | Ant version | |||||||||
| Product Version | SCM revision | ||||||||||
| Review Assigned To | |||||||||||
| Web browser | |||||||||||
| Modules | Core | ||||||||||
| Regression level | |||||||||||
| Regression date | |||||||||||
| Regression introduced in release | |||||||||||
| Regression introduced by commit | |||||||||||
| Triggers an Emergency Pack | No | ||||||||||
| Summary | 0038354: Different string sorting between application and export to spreadsheet process | ||||||||||
| Description | There are some differences by sorting formatted strings between application and export to spreadsheet process. | ||||||||||
| Steps To Reproduce | Open 'Business Partner' window and create new business partners. Enter the same values in search key and commercial name: |100030|50|30 |100030|50|30|100 |100030|50|30|200 |100030|50|300 Those id's are sorted in that order on the application, but when exporting to spreadsheet the sort is different: |100030|50|30 |100030|50|300 |100030|50|30|100 |100030|50|30|200 | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0104229) alostale (manager) 2018-05-03 12:00 edited on: 2018-05-03 14:06 |
When SmartClient receives datasource data, it sorts it again in client side (see ResultSet._handleNewData function) if the data for the applied filters fit in a single page. This ensures same sorting is visualized both when retrieving data from backend and when sorting small datasets in client-side. The problem is, depending on the locales, JavaScript and SQL sorting can differ with some special characters: in this case | is placed before numeric characters in JavaScript but afterwards in SQL. On the other hand, generating CSV is a backend operation so JavaScript sorting is not taken into account. |
|
(0104233) alostale (manager) 2018-05-03 14:07 |
Moving to design defect: there is no a simple solution for this issue. Keeping consistency for all cases between server and client side sorting would require to implement in both places the exact same sorting algorithm taking into consideration different locales. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2018-04-12 15:56 | JONHM | New Issue | |
| 2018-04-12 15:56 | JONHM | Assigned To | => platform |
| 2018-04-12 15:56 | JONHM | Modules | => Core |
| 2018-04-12 15:56 | JONHM | Triggers an Emergency Pack | => No |
| 2018-05-03 12:00 | alostale | Note Added: 0104229 | |
| 2018-05-03 14:06 | alostale | Note Edited: 0104229 | View Revisions |
| 2018-05-03 14:06 | alostale | Status | new => acknowledged |
| 2018-05-03 14:07 | alostale | Note Added: 0104233 | |
| 2018-05-03 14:07 | alostale | Type | defect => design defect |
| 2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |