You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Julius Stroffek (JIRA)" <ji...@apache.org> on 2006/11/15 17:24:38 UTC
[jira] Commented: (DERBY-1434) Client can send incorrect database
name to server after having made multiple connections to different
databases.
[ http://issues.apache.org/jira/browse/DERBY-1434?page=comments#action_12450097 ]
Julius Stroffek commented on DERBY-1434:
----------------------------------------
Sorry for a mess in uploaded files, my connection got broken during first upload.
These file describes my change:
derby1434-try2.diff (attached multiple times, should have the same content)
derby1434-try2.stat
> 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
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.2.1.6, 10.1.3.1
> Reporter: A B
> Assigned To: Julius Stroffek
> Fix For: 10.3.0.0
>
> Attachments: _driver_1, d1434.java, d1434_v2.java, derby-1434-trunk-diff.txt, derby1434-try2.diff, derby1434-try2.diff, derby1434-try2.stat, Server2.trace
>
>
> 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