db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sunitha Kambhampati <ksunitha...@gmail.com>
Subject Re: [jira] Updated: (DERBY-243) connection toString should uniquely identify the connection
Date Fri, 03 Jun 2005 21:15:00 GMT
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

I notice now the output is a little hard to read with all the numbers 
and letters to look at, but I guess thats OK since thats what we decided 
on.

I tried  some simple cases  in ij with different connections and the 
SESSIONID generated is unique and it works fine, but I found one issue 
that on a commit or rollback statement the UUID is not used but instead 
it displays just integers.    David - do you know why ?

Sample - derby.log after applying the patch.
---------------------------------------------------
Database Class Loader started - derby.database.classpath=''
2005-06-03 20:57:12.430 GMT Thread[main,5,main] (XID = 115), (SESSIONID 
= a816c00e-0104-43fe-09d2-0000000c2d90), (DATABASE = tmd), (DRDAID = 
null), Begin compiling prepared statement: insert into t1 values(5) :End 
prepared statement
2005-06-03 20:57:13.481 GMT Thread[main,5,main] (XID = 115), (SESSIONID 
= a816c00e-0104-43fe-09d2-0000000c2d90), (DATABASE = tmd), (DRDAID = 
null), End compiling prepared statement: insert into t1 values(5) :End 
prepared statement
2005-06-03 20:57:13.701 GMT Thread[main,5,main] (XID = 115), (SESSIONID 
= a816c00e-0104-43fe-09d2-0000000c2d90), (DATABASE = tmd), (DRDAID = 
null), Executing prepared statement: insert into t1 values(5) :End 
prepared statement
2005-06-03 20:57:16.646 GMT Thread[main,5,main] (XID = 115), (*SESSIONID 
= 0*), (DATABASE = tmd), (DRDAID = null), Committing

Thanks,
Sunitha.


Mime
View raw message