I'm trying to create SQL Query. If I turn on show SQL and execute the SQL query 'directly' it works fine. But when I run it via Hibernate, I'm getting column not found, because it's append suffixes to all the column names. For example, it's looking for "ID0_" instead of "ID" or "{I}.ID"

If I alias the {I}.ID column as ID0_ I get past that column, and get the same problem on the next one.

Surely this is the way things are supposed to work. Help.

David

You are looking for projection of scalar values in createSQLQuery(). It looks like it is, but it actually isn't supported. We are on it for Hibernate3. Right now, you have to use direct SQL/JDBC via connection() or use HQL.

"projection of scalar values"? If you say so....it just seems to me that query processing code is "poorly written" Why does it use such perverse aliases. -- specifically truncated so small -- ?

I think it's time you read the documentation and figure out what those useless aliases do.

Well, I had read the documentation, just apparently the wrong documentation. And I never said they were useless. I've certainly done the query wrong, but I still think the aliases are "perverse" and am curious about the 'why of it.'? That is, why are the aliases 'truncated so'.

Uhm, _you_ write the aliases. You can use whatever verbose style you like.

(1) uniqueness, when joining many tables
(2) the extremely small alias lengths supported by certain major platforms


Please don't accuse code you don't begin to understand of being "poorly written", unless you want to be banned from the user forum. TIA.

I'm not talking about table aliases, I was talking about column aliases. When I had problems with "SELECT * " I originally enumerated each column, which required me to put "seemingly arbitrary" column aliases in place for Hibernate to fetch them from the resultset.. Changing my qurey to to use "SELECT {X.*},{Y.*}" corrected that problem.