Re: Mismatch in Statement and PreparedStatement execution in Oracle
DB.
Alex Kizub wrote:
You also missed this:
"Any suggestions __except make text match length of the database field
which makes application schema dependent___?"
So, based on this thread, solution should be schema dependent...
If the "requirement" is unrealistic or cannot be met, and actually provides no
value, it shouldn't be a requirement. The OP shouldn't have that requirement.
You might as well as the doctor to cure a broken bone but demand that they not
set it.
One could make the lengths match without hard-coding the length, by using
metadata to determine the length. Still schema dependent, but not hard coded.
That might have been a reasonable requirement.
Whether the OP's requirement as originally stated is reasonable depends on the
answer to my question upthread:
I am curious whether regular database prepared statements would have the
same problem, that is, independently of whether JDBC is involved. Or is
this something that JDBC drivers get wrong?
If the problem is inherent to prepared statements, then nothing can be done at
the Java level except to space-pad the arguments to the correct length.
--
Lew