This content has been marked as final.
Show 4 replies
-
1. Re: Logging PreparedStatement details
nickarls Oct 8, 2012 5:24 AM (in response to prabhun)The PreparedStatement API is a bit poor on the getter side and if the wrapper class has a poor toString(), I think there is not that much that can be done about it, server-side-fetched objects are often proxies. You can of course use reflection on it but it's not a very pretty approach.
-
2. Re: Logging PreparedStatement details
f_marchioni Oct 9, 2012 3:27 AM (in response to prabhun)Well the usual approach to solve this issue is adding a proxy class which can trace JDBC Statements. Time ago I tested it with P6Spy and wrote a small JDBC trace tutorial about it. Give it a try.
Hope it helps
Francesco
-
3. Re: Logging PreparedStatement details
sfcoy Oct 11, 2012 2:22 AM (in response to prabhun)You might get some useful output by setting the driver property: profileSQL=true
-
4. Re: Logging PreparedStatement details
prabhun Oct 11, 2012 4:46 AM (in response to sfcoy)Thanks Nicklas/Francesco/Stephen,
I did tried profileSQL=true, but it gave lots of logging,
Let me try P6Spy and let you know Francesco.
Thanks