Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361569 - Using AlwaysIncludeSortAtBegin or AlwaysIncludeSortAtEnd flag on a column enforces setting the sortIndex to take effect on the sort order.
Summary: Using AlwaysIncludeSortAtBegin or AlwaysIncludeSortAtEnd flag on a column enf...
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Scout (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Vista
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Claudio Guglielmo CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-20 11:38 EDT by Oli Schmid CLA
Modified: 2021-08-19 11:32 EDT (History)
1 user (show)

See Also:
claudio.guglielmo: juno+

Attachments
Write a warning into the LOG when no index is defined. (943 bytes, patch)
2011-10-20 11:39 EDT, Oli Schmid CLA 		claudio.guglielmo: iplog+
Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Oli Schmid CLA 2011-10-20 11:38:42 EDT 
Reproducible: Always

Steps to Reproduce:
1. Define a column on a table page with the flag AlwaysIncludeSortAtBegin  set to true.

2. Ensure the table is filled with data provided by a backend service.

3. Check if the data is really sorted by the defined column.

--> It will not as long as the sortIndex is not defined.

Suggestions: Write at least a warning to the log file when one of the flag is set but no index is defined.
Comment 1 Oli Schmid CLA 2011-10-20 11:39:47 EDT 
Created attachment 205647 [details]
Write a warning into the LOG when no index is defined.

Does the suggested work.
Comment 2 Claudio Guglielmo CLA 2012-05-01 06:52:21 EDT 
Thank you for the patch! It's applied as suggested.
Comment 3 Matthias Zimmermann CLA 2012-07-09 06:50:13 EDT 
ticket closed.
deliverd as part of eclipse scout 3.8.0 (juno release train)