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 "David Van Couvering (JIRA)" <de...@db.apache.org> on 2005/05/16 20:08:06 UTC
[jira] Created: (DERBY-291) Debug VTIs should refer to connection string
Debug VTIs should refer to connection string
--------------------------------------------
Key: DERBY-291
URL: http://issues.apache.org/jira/browse/DERBY-291
Project: Derby
Type: Improvement
Components: Store
Versions: 10.0.2.2
Reporter: David Van Couvering
Priority: Minor
Fix For: 10.0.2.2
Now that the connection toString() provides a unique value, we should display this in VTIs that show data that that can be scoped by connections (such as locks, statement caches, etc.). We should add a column to these VTIs called "connection" which displays the toString() value of the associated connection. This will allow debuggers to correlate particular items in the VTI with particular connections.
--
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
Re: Build broken?
Posted by Satheesh Bandaram <sa...@Sourcery.Org>.
It is not Dag's fault... I briefly broke the build... Now should be
fixed now.
Satheesh
David Van Couvering wrote:
> Just did a fresh pull, ant clobber, ant all, and it works for me. Did
> you do an ant clobber?
>
> David
>
> Dag H. Wanvik wrote:
>
>> Hi,
>> I just did an update, clobber and build and now I can build anymore.
>> I am seeing the problem below. I see this:
>>
>> Compiling 1 source file to /home/dw136774/myderby/trunk/classes
>> /home/dw136774/myderby/trunk/java/client/org/apache/derby/jdbc/ClientXADataSource.java:39:
>> cannot resolve symbol
>> symbol : method setResultSetHoldability (int)
>> location: class org.apache.derby.jdbc.ClientXADataSource
>> this.setResultSetHoldability(CLOSE_CURSORS_AT_COMMIT);
>> ^
>> 1 error
>>
>> BUILD FAILED
>>
>> Anybody experience the same problem?
>> Thanks,
>>
>> Dag
>
>
>
>
Re: Build broken?
Posted by David Van Couvering <Da...@Sun.COM>.
Just did a fresh pull, ant clobber, ant all, and it works for me. Did
you do an ant clobber?
David
Dag H. Wanvik wrote:
> Hi,
> I just did an update, clobber and build and now I can build anymore.
> I am seeing the problem below. I see this:
>
> Compiling 1 source file to /home/dw136774/myderby/trunk/classes
> /home/dw136774/myderby/trunk/java/client/org/apache/derby/jdbc/ClientXADataSource.java:39: cannot resolve symbol
> symbol : method setResultSetHoldability (int)
> location: class org.apache.derby.jdbc.ClientXADataSource
> this.setResultSetHoldability(CLOSE_CURSORS_AT_COMMIT);
> ^
> 1 error
>
> BUILD FAILED
>
> Anybody experience the same problem?
>
> Thanks,
>
> Dag
Build broken?
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
Hi,
I just did an update, clobber and build and now I can build anymore.
I am seeing the problem below. I see this:
Compiling 1 source file to /home/dw136774/myderby/trunk/classes
/home/dw136774/myderby/trunk/java/client/org/apache/derby/jdbc/ClientXADataSource.java:39: cannot resolve symbol
symbol : method setResultSetHoldability (int)
location: class org.apache.derby.jdbc.ClientXADataSource
this.setResultSetHoldability(CLOSE_CURSORS_AT_COMMIT);
^
1 error
BUILD FAILED
Anybody experience the same problem?
Thanks,
Dag
[jira] Updated: (DERBY-291) Debug VTIs should refer to connection string
Posted by "Samuel Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-291?page=all ]
Samuel Andrew McIntyre updated DERBY-291:
-----------------------------------------
Version: 10.1.0.0
Fix Version: 10.1.0.0
(was: 10.0.2.2)
> Debug VTIs should refer to connection string
> --------------------------------------------
>
> Key: DERBY-291
> URL: http://issues.apache.org/jira/browse/DERBY-291
> Project: Derby
> Type: Improvement
> Components: Store
> Versions: 10.1.0.0, 10.0.2.2
> Reporter: David Van Couvering
> Priority: Minor
> Fix For: 10.1.0.0
>
> Now that the connection toString() provides a unique value, we should display this in VTIs that show data that that can be scoped by connections (such as locks, statement caches, etc.). We should add a column to these VTIs called "connection" which displays the toString() value of the associated connection. This will allow debuggers to correlate particular items in the VTI with particular connections.
--
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
[jira] Updated: (DERBY-291) Debug VTIs should refer to connection
string
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-291?page=all ]
Kathey Marsden updated DERBY-291:
---------------------------------
Fix Version/s: (was: 10.2.0.0)
removing from 10.2. see:
http://www.nabble.com/10.2-High-Value-Fix-Candidates-and-Fix-Version-Adjustments-tf2007999.html
> Debug VTIs should refer to connection string
> --------------------------------------------
>
> Key: DERBY-291
> URL: http://issues.apache.org/jira/browse/DERBY-291
> Project: Derby
> Issue Type: Improvement
> Components: Store
> Affects Versions: 10.0.2.2, 10.1.1.0
> Reporter: David Van Couvering
> Priority: Minor
>
> Now that the connection toString() provides a unique value, we should display this in VTIs that show data that that can be scoped by connections (such as locks, statement caches, etc.). We should add a column to these VTIs called "connection" which displays the toString() value of the associated connection. This will allow debuggers to correlate particular items in the VTI with particular connections.
--
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
[jira] Updated: (DERBY-291) Debug VTIs should refer to connection string
Posted by "Samuel Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-291?page=all ]
Samuel Andrew McIntyre updated DERBY-291:
-----------------------------------------
Fix Version: 10.2.0.0
(was: 10.1.0.0)
Environment:
> Debug VTIs should refer to connection string
> --------------------------------------------
>
> Key: DERBY-291
> URL: http://issues.apache.org/jira/browse/DERBY-291
> Project: Derby
> Type: Improvement
> Components: Store
> Versions: 10.0.2.2, 10.1.0.0
> Reporter: David Van Couvering
> Priority: Minor
> Fix For: 10.2.0.0
>
> Now that the connection toString() provides a unique value, we should display this in VTIs that show data that that can be scoped by connections (such as locks, statement caches, etc.). We should add a column to these VTIs called "connection" which displays the toString() value of the associated connection. This will allow debuggers to correlate particular items in the VTI with particular connections.
--
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
[jira] Updated: (DERBY-291) Debug VTIs should refer to connection
string
Posted by "Rick Hillegas (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-291?page=all ]
Rick Hillegas updated DERBY-291:
--------------------------------
Urgency: Low
> Debug VTIs should refer to connection string
> --------------------------------------------
>
> Key: DERBY-291
> URL: http://issues.apache.org/jira/browse/DERBY-291
> Project: Derby
> Issue Type: Improvement
> Components: Store
> Affects Versions: 10.0.2.2, 10.1.1.0
> Reporter: David Van Couvering
> Priority: Minor
> Fix For: 10.2.0.0
>
>
> Now that the connection toString() provides a unique value, we should display this in VTIs that show data that that can be scoped by connections (such as locks, statement caches, etc.). We should add a column to these VTIs called "connection" which displays the toString() value of the associated connection. This will allow debuggers to correlate particular items in the VTI with particular connections.
--
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