You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when executing a SQLInsertClause with setUseLiterals(true), I get a stack trace like this:
com.querydsl.core.QueryException: Caught PSQLException for insert into ddd_it.data_table (data_store_name, primary_key_def, schema_name, table_name)
values ('mydsname', [Ljava.lang.String;@2dc54ad4, 'myschema', 'mytable')
at com.querydsl.sql.DefaultSQLExceptionTranslator.translate(DefaultSQLExceptionTranslator.java:50)
at com.querydsl.sql.Configuration.translate(Configuration.java:508)
at com.querydsl.sql.dml.AbstractSQLInsertClause.execute(AbstractSQLInsertClause.java:436)
at us.catalist.ddd.service.live.LiveDictionaryMaintenanceService.executeModifications(LiveDictionaryMaintenanceService.java:112)
... 25 more
Caused by: org.postgresql.util.PSQLException: ERROR: syntax error at or near "["
Position: 120
Although this works when setUseLiterals(true) is not invoked, it is harder to debug my application because I cannot see what values are bound to the callable statement parameters in the logging. It seems like i could do this through some elaborate code in a SQLListener implementation, but then I am inferring what happened in SQL from elements rather than looking directly at the bound values.
Is there some other way to confirm the bound values on the callable statement that is executed?
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I am using QueryDSL 4.2.1, Postgres 10.5, Java 8.
when executing a
SQLInsertClause
withsetUseLiterals(true)
, I get a stack trace like this:Here is my table definition:
Although this works when
setUseLiterals(true)
is not invoked, it is harder to debug my application because I cannot see what values are bound to the callable statement parameters in the logging. It seems like i could do this through some elaborate code in a SQLListener implementation, but then I am inferring what happened in SQL from elements rather than looking directly at the bound values.Is there some other way to confirm the bound values on the callable statement that is executed?
The text was updated successfully, but these errors were encountered: