Bug 132084 Inconsistent manifest data type for an ODA driver's native data type code
The ODA runtime extension point (org.eclipse.datatools.connectivity.oda.dataSource) schema has defined its dataTypeMapping.nativeDataTypeCode attribute to be an integer value. The oda.util.manifest package, which provides encapsulated access to an ODA runtime extension's plugin manifest, handles such attribute value as a "short" data type. It should be corrected to an "int", to be consistent with its schema definition.
data/org.eclipse.birt.data/src/org/eclipse/birt/data/engine/odaconsumer/Driver.java
return Types.NULL;
		
		String odaType = mapping.getOdaScalarDataType();
		
		if( odaType.equalsIgnoreCase( "Date" ) )
			return Types.DATE;
		else if( odaType.equalsIgnoreCase( "Decimal" ) )
			return Types.DECIMAL;
		else if( odaType.equalsIgnoreCase( "Double" ) )
			return Types.DOUBLE;
		else if( odaType.equalsIgnoreCase( "Integer" ) )
			return Types.INTEGER;
		else if( odaType.equalsIgnoreCase( "String" ) )
			return Types.CHAR;
		else if( odaType.equalsIgnoreCase( "Time" ) )
			return Types.TIME;
		else if( odaType.equalsIgnoreCase( "Timestamp" ) )
			return Types.TIMESTAMP;
		else if( odaType.equalsIgnoreCase( "Blob" ) )
			return Types.BLOB;
		else if( odaType.equalsIgnoreCase( "Clob" ) )
			return Types.CLOB;
		else
		{
			 
			
			sm_logger.logp( Level.WARNING, sm_className, methodName,
					"Invalid ODA data type {0} specified in data source extension mapping.", odaType );
			return Types.NULL;
		}