[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2304) Wrong type detection for sql type char(x) columns
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2304?page=c...
]
Krashan Brahmanjara commented on HHH-2304:
------------------------------------------
Patch for dialect/Dialect.java for correct mapping char to string
registerHibernateType( Types.BIT, Hibernate.BOOLEAN.getName() );
- registerHibernateType( Types.CHAR, Hibernate.CHARACTER.getName() );
+ registerHibernateType( Types.CHAR,1, Hibernate.CHARACTER.getName() );
+ registerHibernateType( Types.CHAR,255, Hibernate.STRING.getName() );
registerHibernateType( Types.DATE, Hibernate.DATE.getName() );
registerHibernateType( Types.DOUBLE, Hibernate.DOUBLE.getName() );
With "length patch" from earlier comment it allow for correct mapping CHAR(?)
column types with Informix drivers.
When patch HHH-3147 will be added will be posiible to read namedQueries without column
names
Wrong type detection for sql type char(x) columns
-------------------------------------------------
Key: HHH-2304
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2304
Project: Hibernate3
Issue Type: Bug
Components: core
Affects Versions: 3.2.0.ga
Environment: Hibernate 3.2.0, Oracle 9.2, Oracle JDBC driver 10.2
Reporter: Markus Heiden
Attachments: hibernate.zip
When executing a sql query which returns columns of sql type char(x), a
java.lang.Character is returned. This leads to returning just the first character of the
value. In my eyes a String should be returned when the char(x) type has a width > 1. I
wasn't able to determine whether this is a jdbc driver issue or a hibernate issue.
When using sql type char(x) for columns of entities no such problems occur.
Test case is attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira