[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2220?page=c...
]
radhakrishna commented on HHH-2220:
-----------------------------------
Same in DB2, if I read a CHARACTER(33) column using session.createSqlQuery("select
character_column from table ") returns me a char ;)
session.createSQLQuery(sql) translates database type CHAR(n) to Java
type char instead of String
------------------------------------------------------------------------------------------------
Key: HHH-2220
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2220
Project: Hibernate Core
Issue Type: Bug
Components: query-sql
Affects Versions: 3.2.0.ga
Reporter: Regis Pires Magalhaes
createSQLQuery() method translates database type CHAR(n) to Java type char instead of
String when using setResultTransformer(Criteria.ALIAS_TO_ENTITY_MAP).
That happens when I do not use addScalar(). And that is the only problem that I have
found when not filling return types in advance.
A workaround I have made is to concatenate the projected field with an empty string
(''). See example below:
...
query.setResultTransformer(Criteria.ALIAS_TO_ENTITY_MAP);
String sqlQuery = "select s.name state from state s where s.name='PI'
";
query = session.createSQLQuery(sqlQuery);
...
result: [{STATE=P}]
name field is CHAR(2) in database definition (PostgreSQL, HSQLDB and Oracle were
tested).
Note that it works when I concatenate the field used in projection with an empty string:
...
String sqlQuery = "select s.name || '' state from state s where
s.name='PI' ";
...
result: [{STATE=PI}]
--
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