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
What version of the product are you using? On what operating system?
1.16 on RHEL 6.5/Windows 7/OS X
Please provide any additional information below.
I have made a modification to expose Properties.DumpFullDebugStackTrace so it
can be modified dynamically at runtime. We find it extremely useful but are not
free to set the system property and restart at will.
I've attached an IntelliJ patch file for reference. This was done from the
current trunk/1.17-SNAPSHOT source. Simply put, I just removed the "final"
designation on the property and added a static setter in the Properties class.
This is just a suggestion. If you feel there's a better implementation please
use it. I feel others could benefit from this type of enhancement as well.
Thanks.
Original issue reported on code.google.com by dsch...@parchment.com on 3 Jun 2014 at 5:31
Would it be OK to have different values of this parameter allowed for different
Connection objects?
Or do you want to be able to change the value of this parameter for a given
Connection object, without acquiring a new one?
If it is the former, then this enhancement could be part of a big update I plan
for Property management.
Original comment by frederic...@gmail.com on 4 Jun 2014 at 11:35
I'm ok with having it for different Connection objects, though the simple use
case is that I just set it true while the system is running (while having
jdbc.sqltiming set at the DEBUG level), acquire the logs with stacks which I'm
after, and toggle it back to false (and set jdbc.sqltiming back to FATAL) so
that the logs don't become too large to reasonably work with.
If your plans for the Property management incorporate a way to do this, that's
great and I look forward to it.
Thanks
Original comment by dsch...@parchment.com on 5 Jun 2014 at 10:11
Original issue reported on code.google.com by
dsch...@parchment.com
on 3 Jun 2014 at 5:31Attachments:
The text was updated successfully, but these errors were encountered: