[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-6313) ClassCastException specifying type="character" in hbm.xml

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6313?page=c... ] Tom Jordahl commented on HHH-6313: ---------------------------------- Here is a test case to reproduces the issue. DB Schema for Table Person (HSQL syntax): CREATE TABLE PEOPLEPERSON(PERSONID BIGINT GENERATED BY DEFAULT AS IDENTITY(START WITH 1) NOT NULL PRIMARY KEY,FIRSTNAME VARCHAR(255),LASTNAME VARCHAR(255),SEX CHAR(1) Query query = session.createQuery("select Person_alias from Person Person_alias where Person_alias.sex = :sex"); query.setParameter("sex", "M"); result = query.list(); Hibernate 3.5 was loose enough to convert the String parameter of length 1 to a Character if and when it was needed. The 3.6 problem comes from the code in VarcharTypeDescriptor.java (actually the overridden doBind() function), which wants to convert what it thinks is a Character type to a string: VarcharTypeDescriptor.java: ~line 52 st.setString( index, javaTypeDescriptor.unwrap( value, String.class, options ) ); In this instance, the "value" type is String, and the "javaTypeDescriptor" is an instance of CharacterTypeDescriptor, which has the following signature for unwrap(): CharacterTypeDescriptor.java: ~line 54 public <X> X unwrap(Character value, Class<X> type, WrapperOptions options) { The class cast come from the VM as a String "value" is passed in to this function, and the signature expects a Character. Arguably this is "user error" because I am passing in an incorrect type (String) for a query parameter that should be a Character. I would say that this should be fixed for the following reasons: - This is breaking backwards compatibility, 3.5 worked. 3.6 doesn't. - This is a very common "mistake" made by users - The system has more than enough information to do the right thing here. When the query parameters are constructed, the NamedParameterDescriptor class has the expectedType and should be able to convert the "value" passed in to doBind() to this expected type. As an alternative, the code that tries to bind the string parameter can detect if the "value" is already of the correct type and NOT call unwrap(). As an example: CharacterTypeDescriptor.java: ~line 54 if (value instanceof String) st.setString( index, value ); else st.setString( index, javaTypeDescriptor.unwrap( value, String.class, options ) ); In our system, we do not have the type information for the query parameters available to us, so as a workaround here is user code that will detect this situation and convert the query param to the right type: query.setParameter(paramName, paramValue); if (paramValue instanceof String && ((String) paramValue).length() == 1) { // Work around Hibernate bug https://hibernate.onjira.com/browse/HHH-6313 // Hibernate 3.5 allowed Strings for character type arguments, 3.6+ is more strict. if (query instanceof QueryImpl) { Type t = ((QueryImpl) query).getParameterMetadata().getNamedParameterExpectedType(paramName); if (t.getName().equals(CharacterType.INSTANCE.getName())) { query.setCharacter(paramName,((String) paramValue).charAt(0)); } } } This code isn't so great, as it has to drop down to QueryImpl to get the job done, but it does work around the issue. Hibernate developer thoughts welcome! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira