[ http://issues.apache.org/jira/browse/DERBY-1434?page=comments#action_12417392 ]
Kathey Marsden commented on DERBY-1434: --------------------------------------- Wish I could delete the comment but the early closed result set with is issue is not a valid symptom. This wrong line caused the test to fail. Should have been ps2. ResultSet rs2 = ps.executeQuery(); > Client can send incorrect database name to server after having made multiple > connections to different databases. > ---------------------------------------------------------------------------------------------------------------- > > Key: DERBY-1434 > URL: http://issues.apache.org/jira/browse/DERBY-1434 > Project: Derby > Type: Bug > Components: Network Client > Versions: 10.2.0.0, 10.1.3.0, 10.1.2.5 > Reporter: A B > Fix For: 10.2.0.0 > Attachments: Server2.trace, _driver_1, d1434.java > > I have a simple program that connects to a database using the Derby Client, > executes a simple query, then connects to a different database using a > different Connection object and executes another simple query on that second > connection. The queries both execute without error, so it appears that the > connections are correct--i.e. each query will only work on one of the > databases, and both queries work, therefore each must be getting executed > against the correct database. > But in looking at the client and server traces, I noticed that for the query > on the second database, the client is actually sending the name of the > *first* database as RDBNAM, which (I think?) is wrong--it should be sending > the name of the second database, since the query is being executed on the > second Connection object. > This behavior does not appear to occur for JCC. -- 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
