0

I am using JPA hibernate, with postgres. Problem arises on trying to run getResultList() on javax.persistence.Query. The query is small about 10 lines but with joins and around 80 columns in each of the two tables queried it balloons to around 200 lines of JBOSS logs. Something like below.

15:47:05,908 INFO  [stdout] (Thread-11 (HornetQ-client-global-threads-507424984)) Hibernate: 
15:47:05,910 INFO  [stdout] (Thread-11 (HornetQ-client-global-threads-507424984))     select
15:47:05,911 INFO  [stdout] (Thread-11 (HornetQ-client-global-threads-507424984))         tablename0_.some_field_name as auto_genrated_field_name,
....
15:47:06,255 WARN  [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (Thread-11 (HornetQ-client-global-threads-507424984)) SQL Error: 0, SQLState: 42883
15:47:06,256 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (Thread-11 (HornetQ-client-global-threads-507424984)) ERROR: operator does not exist: character varying ~~ integer
Hint: No operator matches the given name and argument type(s). You might need to add explicit type casts.
Position: 7236

As seen, the log does not tell me exactly which field name the type conversion is having the problem, but only the character position which it thinks is wrong. As per the indentation and the way hibernate formats my query I cannot be sure which variable it is referring to. I actually tried putting this exact query log onto an editor and then take me to that character position, but I am not sure if I am looking at the right place. I have also looked in Eclipse debugger and the parameter types match, when creating the query.

Is there any switch in JBOSS logs, or configuration that would tell me exactly which field I am getting wrong.

Soham
  • 671
  • 1
  • 7
  • 23

1 Answers1

0

You can try with the solution provided here: How to view the SQL queries issued by JPA?

Did you look into the PostgreSQL log? The statements causing errors are logged by default.

Community
  • 1
  • 1
Tomasz Siorek
  • 701
  • 5
  • 10
  • Thanks for the answer. I did not try any of those switches, but just plopped the entire query string produced by JPA, into PGADMIN and then edited out the log statements, to zoom into the error. – Soham Jul 30 '14 at 22:04