Hibernate version: 3.1.3

Mapping documents: does not matter.

Name and version of the database you are using: PostgreSQL 8.1.3

The generated SQL (show_sql=true):

Hello, I have search forum before ask it, but I can't found a answer to my problem. We have used ilike operator in Hibernate 2.x and now, we are migrating to Hibernate 3.1.3 and ilike don't works anymore. I could correct a ton of HQL using some tool to do a replace but so, my queries will be not case insensitive. The scenario is:
1. Use criteria will take a lot of time because we must replace any query by code to use Criteria;
2. use "lower", "upper" functions will need a great effort to rewrite a ton of queries;
3. We have try to use query.substitutions in the following way:

"random" works fine, but "like=ilike" don't. There is something wrong with query parser or I have missed some detail about query.substitutions? The docs say: "Mapping from tokens in Hibernate queries to SQL tokens"

What I have done wrong? :-(

Kind regards.

You have done nothing wrong as such just caught up with a change in the parser. H3 uses a formal parser that is making sure the tokens are correct while H2 passed through anything it did not understand. ilike is not a reserved word so it H2 would pass it through and H3 will complain as it was expecting a valid token. H3 is correct in its approach.

David, thanks, I catch it. :-)

But, how can I transpasse this chance in parser without doing a lot of work? I think that "query.substitutions" must work for my case, but it didn't. I wonder to know why random is replaced by "random()" and "like" is not replaced by "ilike".

Which approach you suggest to my case?

Kind Regads