Bug 350763 User-defined Sort Hints in a data set got overwritten in a SQB design session
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.
data/org.eclipse.birt.report.data.oda.jdbc.dbprofile.ui/src/org/eclipse/birt/report/data/oda/jdbc/dbprofile/ui/internal/sqb/SQLQueryUtility.java
if( varDataType instanceof ExactNumericDataType )
            {
                elementAttrs.setScale( ((ExactNumericDataType) varDataType).getScale() );
            }
        }
        
        if( var.getLabel() != null )
            elementAttrs.setUiDisplayName( var.getLabel() );
        if( var.getDescription() != null )
            elementAttrs.setUiDescription( var.getDescription() );
    }
    
    private static int toJDBCTypeCode( DataType varDataType )
    {
        return SQLDataTypeUtility.toJDBCTypeCode( varDataType );
    }
    /**
     * Process the parameter definition to handle special use, such as setting
     * a null native data type to a String by default.
     */
    private static void adjustParameterDefinition( ParameterDefinition paramDefn )
    {
        assert( paramDefn != null );
        DataElementAttributes paramAttributes = paramDefn.getAttributes();
        if( paramAttributes == null )
            return;     
        if( paramAttributes.getNativeDataTypeCode( ) == Types.NULL )
            paramAttributes.setNativeDataTypeCode( Types.CHAR );