[ http://issues.apache.org/jira/browse/DERBY-243?page=all ]
David Van Couvering updated DERBY-243:
--------------------------------------
Attachment: DERBY-243.diff
Good catch by Kathey. I added some SQL to lang/miscerrors.sql to print out all
the rows
from the error log using the ErrorLogReader VTI, and it printed out the new ID
fine,
except that it was truncated because the column length for the id was 15 when
it needs
to be 36 for a UUID.
I am attaching an updated patch that resolves this issue.
I modified the ErrorLogReader VTI to set the length to 36, and the data printed
out
fine. I also include the change to miscerrors.sql so that we are excercising
this
VTI in our regression tests.
Thanks, Kathey!
David
> connection toString should uniquely identify the connection
> -----------------------------------------------------------
>
> Key: DERBY-243
> URL: http://issues.apache.org/jira/browse/DERBY-243
> Project: Derby
> Type: Improvement
> Components: JDBC
> Reporter: Kathey Marsden
> Assignee: David Van Couvering
> Priority: Trivial
> Fix For: 10.0.2.1, 10.0.2.0, 10.0.2.2, 10.1.0.0
> Attachments: DERBY-243.diff
>
> The toString() on the Derby connection doesn't print
> unique information.
> for example System.out.println(conn) prints:
> EmbedConnection in the case of derby embedded
> It would be great if the toString() method for connections could be used to
> differentiate one connection from another.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
