I've recently upgrade from hibernate 3.5 to 4.3.11 with Spring 4.3.9 Before the upgrade everything was working fine. After the upgrade I get this error.
Environment: Java 8, Tomcat 7.0.23, Hibernate 4.3.11, Spring 4.3.9, MSSQL Server 2008,

While executing the following sql query through hibernate, we are getting list of null object with correct size in the list but object are null.

Query:
select DISTINCT(HIERARCHY_ID) from BASETYPE_HIERARCHY_MAPPING
where BASETYPE_ID IN (select BASETYPE_ID from BASETYPE_GROUP_MAPPING
where GROUP_ID IN (select GROUP_ID from USER_GROUP_MAPPING where USER_ID like(select ID from USER where USERID='7')))

Java Code:
String sqlQuery="select DISTINCT(HIERARCHY_ID) from BASETYPE_HIERARCHY_MAPPING where BASETYPE_ID IN "
+ "(select BASETYPE_ID from BASETYPE_GROUP_MAPPING where GROUP_ID IN "
+ "(select GROUP_ID from USER_GROUP_MAPPING where USER_ID=(select ID from USER where USERID=:userId)))";
Query query = session.createSQLQuery(sqlQuery);
query.setParameter("userId", userId);
List<String> typeId = query.list();

In result list of null objects.I have found similar type of issue for HQL(solution was mistake in mapping) but its simple sql query.

Try to debug it and see what the JDBC ResultSet contains. Most likely, the column was not fetched properly. Try checking the column case or run the query in the SQL console to see if it works.

I have already done that, SQL query is working fine in SQL console. I have already mention that , it was working in hibernate 3.5, after upgrading the version hibernate 4.4 it is not working.

Is it the HIERARCHY_ID really a String? That's a curious thing.

Otherwise, the SQL query looks fine. You should debug and see why it is not working because there is no indication why it shouldn't run as expected.

By the way, Hibernate 4 is no longer supported, so, if you want to benefit from bug fixes, you will have to upgrade to 5.2.

Yes it is String Type.

Solved the problem using hibernate scalar, by specifying the return type of column in query.
addScalar()

Following changes are done in java code to solve the issue:


But in our project lot of sql queries used, so I need to change in all queires any better soluation instead of this addScalar() or why its mandatory from hibernate 4, it was working fine in 3.5. Why we should mention type for every column ? As per Hibernate Documentation it's not mandatory.

I tested it with Hibernate 5.2, and it works just fine. I won't test it for 4.x because, as I told you before, it's no longer supported.

Thanks for quick reply. I have tested on 5.1.10 still its getting same issue. I can't upgrade to 5.2 because lot of changes in 5.2 version JPA queries & all.

Only Hibernate 5.2 issues will be fixed, so you have to provide a replicating test case for 5.2.

Sometimes, fixes get backported, so it might get into 5.1 or 5.0. However, there's little chance it will be backported to 4.x.

If you want to get this integrated like ASAP, then send us a Pull Request with a fix.

I'm glad you got it fixed.