Home/ Questions/Q 166329
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T12:04:43+00:00

I had a really huge problem recently which took me a lot of time

  • 0

I had a really huge problem recently which took me a lot of time to debug. I have an update statement which updates 32 columns in table. I did that with PreparedStatement. Accidentaly I deleted one setParameter() call so update could not be finished successfully.

I got exception from JDBC (Apache Derby) telling: ‘At leas one parameter is not initialized’ and was not able to figure out which parameter is not set since driver would not tell you nothing about name or ordinal number of at least first parameter which is not set…

I was googleing unsuccessfully for some utility which will produce plain old SQL out of (nearly-finished) prepared statement. It would help a lot in situations like this one, since I will be able to see what is not set.

Have anyone faced this problem? Got any solution?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Since the parameters in a prepared statement are just a List or Map in the PreparedStatement Object you should be able to inspect the values.

    Also you could write a very simple Wrapper around you jdbc driver that creates wrapped PreparedStatements and logs all parameters and there settings before actually executing the statement.

    • 0