Community
Participate
Working Groups
When editing a data set in the Data Set Editor, an user may add own user-defined Sort Hints. But each time an user activates the SQB designer page in DSE, those sort hints always got overwritten and replaced by the sort keys defined in the query's OrderBy clause. This is expected behavior if the OrderBy clause gets changed, as it is not clear how a revised OrderBy clause relates to those user-defined sort hints. However, if the OrderBy clause did not get changed, the previously defined sort hints should be preserved.
Delivered fix in org.eclipse.birt.report.data.oda.jdbc.dbprofile.ui. It now checks that if the OrderBy clause did not get changed in a SQB design session, and will then preserve the SortSpecification provided by the ODA host in a session request. If the OrderBy clause did get changed, its sort keys will continue to replace the data set sort hints; and users will have to redefine any sort hints that are still applicable on top of the revised OrderBy clause.
Resolved.
