|
I get the feeling the following point may have been missed, so
resending. I found one issue that on a commit or rollback statement the UUID is not used but instead it displays just integers. So in the log below it is hard to know on which connection, the commit was issued. It is important to be able to match the commit and abort statements right. And in the simple log below I dont see the UUID tied right with the commit statement. David - do you know why. I think it needs to be fixed too. Thanks, Sunitha. Sunitha Kambhampati wrote: Although I havent looked at the diffs yet, but I applied the patch in Derby-243 to see how the derby.log would look with derby.language.logStatementText=true |
- Re: [jira] Updated: (DERBY-243) connection toSt... Sunitha Kambhampati
- Re: [jira] Updated: (DERBY-243) connection... David Van Couvering
- Re: [jira] Updated: (DERBY-243) connection... David Van Couvering
- Re: [jira] Updated: (DERBY-243) connection... Øystein Grøvlen
- Re: [jira] Updated: (DERBY-243) connec... Øystein Grøvlen
- Re: [jira] Updated: (DERBY-243) connection... Øystein Grøvlen
- Re: [jira] Updated: (DERBY-243) connec... David Van Couvering
- Re: [jira] Updated: (DERBY-243) co... Øystein Grøvlen
- [jira] Updated: (DERBY-243) connection toS... David Van Couvering (JIRA)
- Re: [jira] Updated: (DERBY-243) connec... Øystein Grøvlen
- Re: [jira] Updated: (DERBY-243) co... David Van Couvering
