|
|
Sponsor |
[jira] Updated: (DERBY-243) connection toString should uniquely identify th: msg#00553apache.db.derby.devel
[ http://issues.apache.org/jira/browse/DERBY-243?page=all ] Kathey Marsden updated DERBY-243: --------------------------------- Summary: connection toString should uniquely identify the connection (was: connection toString doesn't give enough information) Description: 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. was: 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 I am not sure if XA Connections and Pooled Connections have the same issue. I didn't immediately see an override of the toString() method in BrokeredConnection.java like there is for EmbedConnection > 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 > > 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
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: [jira] Commented: (DERBY-214) Remove System.exit() calls from the DB2jServerImpl.java, Kathey Marsden |
|---|---|
| Next by Date: | Re: [jira] Commented: (DERBY-214) Remove System.exit() calls from the DB2jServerImpl.java, David Van Couvering |
| Previous by Thread: | Re: [jira] Created: (DERBY-243) connection toString doesn't give enough information, David Van Couvering |
| Next by Thread: | Contributing to Derby, Tips and Tasks To Get You Started, Kathey Marsden |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
Free MagazinesCisco NewsReceive a free quarterly e-newsletter with exclusive articles on how Cisco IT uses its own products and solutions to enable the business. subscribe Systems Management News, the newspaper for IT systems administration and data center managers! Each issue of Systems Management News is chock-full of news and analysis to help you understand what's happening in your field. subscribe The Enterprise Newsweekly eWeek is the essential technology information source for builders of e-business. subscribe Oracle Magazine Oracle Magazine contains technology strategy articles, sample code, tips, Oracle and partner news, how to articles for developers and DBAs, and more. Oracle (NASDAQ: ORCL) is the world's largest enterprise software company. subscribe Total Telecom Total Telecom is "The Economist of the communications industry". subscribe |
Home | sitemap
| advertise | OSDir is
an inevitable website.
|