Re: Jenkins build is still unstable: Derby-trunk #1888

On 7/10/2013 8:36 PM, Apache Jenkins Server wrote: See I think this may be a new JavaDoc warning: OptimizerPlan.java:93, JavaDoc Tool, Priority: Normal @param argument "fromListSize" is not a parameter name. thanks, bryan

[jira] [Commented] (DERBY-6291) Improve code coverage of org.apache.derby.iapi.jdbc.BrokeredCallableStatement

[ https://issues.apache.org/jira/browse/DERBY-6291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705423#comment-13705423 ] Bryan Pendleton commented on DERBY-6291: Hi Ahsan, thanks for logging this i

[jira] [Resolved] (DERBY-6284) Improve test coverage of org.apache.derby.iapi.db.ConnectionInfo

[ https://issues.apache.org/jira/browse/DERBY-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton resolved DERBY-6284. Resolution: Fixed Fix Version/s: 10.11.0.0 Committed revision 1502089. Thank you

[jira] [Commented] (DERBY-6284) Improve test coverage of org.apache.derby.iapi.db.ConnectionInfo

[ https://issues.apache.org/jira/browse/DERBY-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704581#comment-13704581 ] Bryan Pendleton commented on DERBY-6284: Great! I don't think there&#

[jira] [Commented] (DERBY-6288) Skip 10.0.2.1 in upgrade tests when running with JaCoCo

[ https://issues.apache.org/jira/browse/DERBY-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702881#comment-13702881 ] Bryan Pendleton commented on DERBY-6288: Patch eliminates the exception fo

[jira] [Updated] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open

[ https://issues.apache.org/jira/browse/DERBY-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-6216: --- Attachment: noMemberField.diff Attached 'noMemberField.diff' patch proposal f

Re: Automated test runs of the trunk using JaCoCo?

I'm looking into setting up automatic runs with JaCoCo and have a partially working setup. The EMMA runs use multiple JVMs to cover all JDBC drivers and optional modules, but I've only set up JaCoCo with Java 7 for now. I think the results are useful nevertheless, so I'll see if I can get them pub

Jacoco exception

When I run the following: ant -Dderby.junit.testclass=org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite jacoco-junit-single I get an internal exception thrown out of the JaCoCo dynamic instrumentation runtime (see below). Does this occur for anyone else? Do you think this indic

Automated test runs of the trunk using JaCoCo?

I've made significant use of the automated Emma test runs at: http://dbtg.foundry.sun.com/derby/test/coverage/index.html and I'm grateful to the community members who provide this resource. I wonder; given that the Emma tool appears to have fallen into disrepair, whether the automated tool could

[jira] [Commented] (DERBY-6284) Improve test coverage of org.apache.derby.iapi.db.ConnectionInfo

[ https://issues.apache.org/jira/browse/DERBY-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700962#comment-13700962 ] Bryan Pendleton commented on DERBY-6284: Indeed, when I run TableFunction

[jira] [Commented] (DERBY-6284) Improve test coverage of org.apache.derby.iapi.db.ConnectionInfo

[ https://issues.apache.org/jira/browse/DERBY-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700223#comment-13700223 ] Bryan Pendleton commented on DERBY-6284: Using the debugger, I verified

[jira] [Commented] (DERBY-6284) Improve test coverage of org.apache.derby.iapi.db.ConnectionInfo

[ https://issues.apache.org/jira/browse/DERBY-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700160#comment-13700160 ] Bryan Pendleton commented on DERBY-6284: I've been studying this

[jira] [Commented] (DERBY-6267) Add ability to compactly specify a complete query plan in an optimizer override.

[ https://issues.apache.org/jira/browse/DERBY-6267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13699053#comment-13699053 ] Bryan Pendleton commented on DERBY-6267: Thanks Rick, It's clear

[jira] [Commented] (DERBY-6267) Add ability to compactly specify a complete query plan in an optimizer override.

[ https://issues.apache.org/jira/browse/DERBY-6267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13698358#comment-13698358 ] Bryan Pendleton commented on DERBY-6267: > It would be nice to be

[jira] [Updated] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open

[ https://issues.apache.org/jira/browse/DERBY-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-6216: --- Attachment: preparedTests.diff I added several tests of the behavior with PreparedStatements

[jira] [Commented] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open

[ https://issues.apache.org/jira/browse/DERBY-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696828#comment-13696828 ] Bryan Pendleton commented on DERBY-6216: Good catch on the PreparedState

[jira] [Commented] (DERBY-6284) Improve test coverage of org.apache.derby.iapi.db.ConnectionInfo

[ https://issues.apache.org/jira/browse/DERBY-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696449#comment-13696449 ] Bryan Pendleton commented on DERBY-6284: Here is the current coverage report

[jira] [Created] (DERBY-6284) Improve test coverage of org.apache.derby.iapi.db.ConnectionInfo

Bryan Pendleton created DERBY-6284: -- Summary: Improve test coverage of org.apache.derby.iapi.db.ConnectionInfo Key: DERBY-6284 URL: https://issues.apache.org/jira/browse/DERBY-6284 Project: Derby

[jira] [Updated] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open

[ https://issues.apache.org/jira/browse/DERBY-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-6216: --- Issue & fix info: Patch Available,Repro attached By the way, it's not obvious t

[jira] [Updated] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open

[ https://issues.apache.org/jira/browse/DERBY-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-6216: --- Attachment: xplain-only.diff OK, I think I've finally got a patch worth consideration b

[jira] [Commented] (DERBY-6211) Make Optimizer trace logic pluggable.

[ https://issues.apache.org/jira/browse/DERBY-6211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695217#comment-13695217 ] Bryan Pendleton commented on DERBY-6211: Hi Rick, Do you think it is a com

[jira] [Resolved] (DERBY-6264) Improve test coverage of org.apache.derby.iapi.db.PropertyInfo

[ https://issues.apache.org/jira/browse/DERBY-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton resolved DERBY-6264. Resolution: Fixed The patch looks fine to me, and matches our discussion. I built with the

[jira] [Commented] (DERBY-6264) Improve test coverage of org.apache.derby.iapi.db.PropertyInfo

[ https://issues.apache.org/jira/browse/DERBY-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693962#comment-13693962 ] Bryan Pendleton commented on DERBY-6264: Thanks Ahsan, this looks great!

[jira] [Updated] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open

[ https://issues.apache.org/jira/browse/DERBY-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-6216: --- Attachment: emptyRS.diff I think that the approach suggested by Knut Anders is promising

[jira] [Assigned] (DERBY-4493) encryptionAlgorithm is ignored at boot, but Documentation states it is required

[ https://issues.apache.org/jira/browse/DERBY-4493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton reassigned DERBY-4493: -- Assignee: (was: Bryan Pendleton) Wow I forgot about this one! I'm not act

[jira] [Commented] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open

[ https://issues.apache.org/jira/browse/DERBY-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691992#comment-13691992 ] Bryan Pendleton commented on DERBY-6216: Yes, I like that suggestion. I'

[jira] [Commented] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open

[ https://issues.apache.org/jira/browse/DERBY-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691018#comment-13691018 ] Bryan Pendleton commented on DERBY-6216: OK, I think it's more complic

[jira] [Commented] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open

[ https://issues.apache.org/jira/browse/DERBY-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691011#comment-13691011 ] Bryan Pendleton commented on DERBY-6216: So here, I think, is the place where

[jira] [Updated] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open

[ https://issues.apache.org/jira/browse/DERBY-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-6216: --- Attachment: addTests.diff So I wonder if there are differences in behavior here between

[jira] [Commented] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open

[ https://issues.apache.org/jira/browse/DERBY-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690978#comment-13690978 ] Bryan Pendleton commented on DERBY-6216: Thanks Dag! I knew it had been too

[jira] [Commented] (DERBY-6264) Improve test coverage of org.apache.derby.iapi.db.PropertyInfo

[ https://issues.apache.org/jira/browse/DERBY-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689689#comment-13689689 ] Bryan Pendleton commented on DERBY-6264: I am looking at:

[jira] [Commented] (DERBY-6264) Improve test coverage of org.apache.derby.iapi.db.PropertyInfo

[ https://issues.apache.org/jira/browse/DERBY-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688848#comment-13688848 ] Bryan Pendleton commented on DERBY-6264: Hi Ahsan, I agree, it is not obv

[jira] [Commented] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open

[ https://issues.apache.org/jira/browse/DERBY-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686197#comment-13686197 ] Bryan Pendleton commented on DERBY-6216: It's clearly been a whil

[jira] [Commented] (DERBY-6262) Simplify message-generating methods using varargs

[ https://issues.apache.org/jira/browse/DERBY-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13685952#comment-13685952 ] Bryan Pendleton commented on DERBY-6262: Nice simplification, and a

Code archaeology question about TestPropertyInfo class

Hi all, In the context of https://issues.apache.org/jira/browse/DERBY-6264 Ahsan and I have been discussing the class: org.apache.derbyTesting.functionTests.util.TestPropertyInfo We cannot find much information about this class and its use. We suggest that perhaps we could just remove this c

Re: how to use the PlanExporter tool

Does this mean that we should be calling this.close() rather than source.close()? thanks, bryan On Mon, Jun 17, 2013 at 8:51 AM, Knut Anders Hatlen wrote: > shortcut so that NoPutResultSetImpl.close() is not invoked: > > /* Nothing to do if open was short circuited by false constant > exp

[jira] [Assigned] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open

[ https://issues.apache.org/jira/browse/DERBY-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton reassigned DERBY-6216: -- Assignee: Bryan Pendleton > XPLAIN feature does not work and gives ERROR XC

[jira] [Commented] (DERBY-6264) Improve test coverage of org.apache.derby.iapi.db.PropertyInfo

[ https://issues.apache.org/jira/browse/DERBY-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13684252#comment-13684252 ] Bryan Pendleton commented on DERBY-6264: Here are a number of possibilitie

[jira] [Commented] (DERBY-6264) Improve test coverage of org.apache.derby.iapi.db.PropertyInfo

[ https://issues.apache.org/jira/browse/DERBY-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13684247#comment-13684247 ] Bryan Pendleton commented on DERBY-6264: I am confused about the Property

[jira] [Created] (DERBY-6264) Improve test coverage of org.apache.derby.iapi.db.PropertyInfo

Bryan Pendleton created DERBY-6264: -- Summary: Improve test coverage of org.apache.derby.iapi.db.PropertyInfo Key: DERBY-6264 URL: https://issues.apache.org/jira/browse/DERBY-6264 Project: Derby

[jira] [Resolved] (DERBY-6257) Update link to Subversion home page on http://db.apache.org/derby/dev/derby_source.html

[ https://issues.apache.org/jira/browse/DERBY-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton resolved DERBY-6257. Resolution: Fixed Update is live on the web site. > Update link

[jira] [Closed] (DERBY-6257) Update link to Subversion home page on http://db.apache.org/derby/dev/derby_source.html

[ https://issues.apache.org/jira/browse/DERBY-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton closed DERBY-6257. -- > Update link to Subversion home page on > http://db.apache.org/derby/dev/derby_sourc

[jira] [Commented] (DERBY-6257) Update link to Subversion home page on http://db.apache.org/derby/dev/derby_source.html

[ https://issues.apache.org/jira/browse/DERBY-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13684009#comment-13684009 ] Bryan Pendleton commented on DERBY-6257: I'm not sure the automatic

[jira] [Commented] (DERBY-6257) Update link to Subversion home page on http://db.apache.org/derby/dev/derby_source.html

[ https://issues.apache.org/jira/browse/DERBY-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13684005#comment-13684005 ] Bryan Pendleton commented on DERBY-6257: I tried the single combined commit a

[jira] [Updated] (DERBY-6164) Improve Derby's Code Coverage - GSoC 2013 Project

[ https://issues.apache.org/jira/browse/DERBY-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-6164: --- Assignee: ahsan shamsudeen (was: Bryan Pendleton) > Improve Derby's Code

[jira] [Commented] (DERBY-6164) Improve Derby's Code Coverage - GSoC 2013 Project

[ https://issues.apache.org/jira/browse/DERBY-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683020#comment-13683020 ] Bryan Pendleton commented on DERBY-6164: Thanks Myrna, that's a good

[jira] [Commented] (DERBY-6257) Update link to Subversion home page on http://db.apache.org/derby/dev/derby_source.html

[ https://issues.apache.org/jira/browse/DERBY-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681782#comment-13681782 ] Bryan Pendleton commented on DERBY-6257: Thanks Knut! I see that I was lookin

[jira] [Updated] (DERBY-6257) Update link to Subversion home page on http://db.apache.org/derby/dev/derby_source.html

[ https://issues.apache.org/jira/browse/DERBY-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-6257: --- Attachment: docs.diff I think we just have to change the link in derby_source.html

[jira] [Created] (DERBY-6257) Update link to Subversion home page on http://db.apache.org/derby/dev/derby_source.html

Bryan Pendleton created DERBY-6257: -- Summary: Update link to Subversion home page on http://db.apache.org/derby/dev/derby_source.html Key: DERBY-6257 URL: https://issues.apache.org/jira/browse/DERBY-6257

[jira] [Commented] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open

[ https://issues.apache.org/jira/browse/DERBY-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661385#comment-13661385 ] Bryan Pendleton commented on DERBY-6216: I think that the basic idea was

[jira] [Commented] (DERBY-6216) XPLAIN feature does not work and gives ERROR XCL16: ResultSet not open

[ https://issues.apache.org/jira/browse/DERBY-6216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661379#comment-13661379 ] Bryan Pendleton commented on DERBY-6216: Urk. Sorry about that. At least th

[jira] [Commented] (DERBY-6222) add release note for 10.11 noting that using a JVM previous to jdk1.6 will not work

[ https://issues.apache.org/jira/browse/DERBY-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655566#comment-13655566 ] Bryan Pendleton commented on DERBY-6222: That sounds fine to me. Thanks for

[jira] [Commented] (DERBY-6222) add release note for 10.11 noting that using a JVM previous to jdk1.6 will not work

[ https://issues.apache.org/jira/browse/DERBY-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655308#comment-13655308 ] Bryan Pendleton commented on DERBY-6222: Can't we detect a 1.5 JVM and

Re: Does the XPLAIN feature work in Derby 10.9.1.0

I get the same result: $ java -cp ~/derby/db-derby-10.9.1.0-bin/lib/derbyrun.jar org.apache.derby.tools.ij ij version 10.9 ij> connect 'jdbc:derby:xplaindb;create=true'; ij> call syscs_util.syscs_set_runtimestatistics(1); 0 rows inserted/updated/deleted ij> call syscs_util.syscs_set_xplain_sch

[jira] [Commented] (DERBY-6164) Improve Derby's Code Coverage - GSoC 2013 Project

[ https://issues.apache.org/jira/browse/DERBY-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647699#comment-13647699 ] Bryan Pendleton commented on DERBY-6164: Hi Ahsan, I noticed that there are

[jira] [Commented] (DERBY-6164) Improve Derby's Code Coverage - GSoC 2013 Project

[ https://issues.apache.org/jira/browse/DERBY-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647526#comment-13647526 ] Bryan Pendleton commented on DERBY-6164: Also, DERBY-6211 is relevant to

Does "nabble" still exist? Does it still carry derby-dev?

The "nabble" links on http://db.apache.org/derby/derby_mail.html don't seem to work anymore. The gmane, MarkMail, and mod_mbox links seem fine, though. If nabble is dead, we should probably remove the links. thanks, bryan

[jira] [Commented] (DERBY-6164) Improve Derby's Code Coverage - GSoC 2013 Project

[ https://issues.apache.org/jira/browse/DERBY-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647518#comment-13647518 ] Bryan Pendleton commented on DERBY-6164: Ahsan, are you subscribed to the d

Re: [VOTE] Sunsetting support for Java 5 and CDC

On 04/30/2013 07:48 AM, Rick Hillegas wrote: Please vote on the following proposed policy for supported platforms. This seems like a rational process for moving forward. +1 bryan

Is IndexStatisticsDaemonImpl tested by our regression suite?

Hi all, While discussing DERBY-6164 with Ahsan, we noticed that the IndexStatisticsDaemonImpl class is listed in our coverage reports as being substantially under-tested: http://dbtg.foundry.sun.com/derby/test/coverage/_files/6d.html Does anyone know if the coverage report is accurate here? Is

[jira] [Commented] (DERBY-6164) Improve Derby's Code Coverage - GSoC 2013 Project

[ https://issues.apache.org/jira/browse/DERBY-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646227#comment-13646227 ] Bryan Pendleton commented on DERBY-6164: Hi Ahsan, I think your proposal l

[jira] [Commented] (DERBY-6164) Improve Derby's Code Coverage - GSoC 2013 Project

[ https://issues.apache.org/jira/browse/DERBY-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644505#comment-13644505 ] Bryan Pendleton commented on DERBY-6164: That's great, it looks like you

[jira] [Commented] (DERBY-6164) Improve Derby's Code Coverage - GSoC 2013 Project

[ https://issues.apache.org/jira/browse/DERBY-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641321#comment-13641321 ] Bryan Pendleton commented on DERBY-6164: Hello Ahsan, I am glad to hear

[jira] [Commented] (DERBY-6164) Improve Derby's Code Coverage - GSoC 2013 Project

[ https://issues.apache.org/jira/browse/DERBY-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13638740#comment-13638740 ] Bryan Pendleton commented on DERBY-6164: Hi Ahsan, Can you report on the e

[jira] [Commented] (DERBY-6164) Improve Derby's Code Coverage - GSoC 2013 Project

[ https://issues.apache.org/jira/browse/DERBY-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634052#comment-13634052 ] Bryan Pendleton commented on DERBY-6164: Another thing you can try is to down

[jira] [Commented] (DERBY-6164) Improve Derby's Code Coverage - GSoC 2013 Project

[ https://issues.apache.org/jira/browse/DERBY-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634050#comment-13634050 ] Bryan Pendleton commented on DERBY-6164: I thought that the ant build scr

[jira] [Commented] (DERBY-6164) Improve Derby's Code Coverage - GSoC 2013 Project

[ https://issues.apache.org/jira/browse/DERBY-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632849#comment-13632849 ] Bryan Pendleton commented on DERBY-6164: Hello, Ahsan, I am glad to hear you

Re: [VOTE] 10.10.1.1 release

Please test-drive the 10.10.1.1 candidate, then vote on whether to accept it as a Derby release. +1 to this release; thanks all for the hard work! I share the community's concern with DERBY-6092; however I think that JDK 1.5 is quite old now, and users who might encounter DERBY-6092 can find s

[jira] [Updated] (DERBY-6164) Improve Derby's Code Coverage - GSoC 2013 Project

[ https://issues.apache.org/jira/browse/DERBY-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-6164: --- Description: This year's edition of Google Summer of Code includes, once again, the A

[jira] [Created] (DERBY-6164) Improve Derby's Code Coverage - GSoC 2013 Project

Bryan Pendleton created DERBY-6164: -- Summary: Improve Derby's Code Coverage - GSoC 2013 Project Key: DERBY-6164 URL: https://issues.apache.org/jira/browse/DERBY-6164 Project: Derby

[jira] [Assigned] (DERBY-6164) Improve Derby's Code Coverage - GSoC 2013 Project

[ https://issues.apache.org/jira/browse/DERBY-6164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton reassigned DERBY-6164: -- Assignee: Bryan Pendleton > Improve Derby's Code Coverage - GSoC 2013

[jira] [Commented] (DERBY-6092) testPositionAgressive(org.apache.derbyTesting.functionTests.tests.jdbcapi.BlobClob4BlobTest)j fails with : 'The handle is invalid.: java.io.IOException'.

[ https://issues.apache.org/jira/browse/DERBY-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625366#comment-13625366 ] Bryan Pendleton commented on DERBY-6092: Including the queries both with

[jira] [Commented] (DERBY-6069) Derby doesn't export the version number in its OSGI exported packages

[ https://issues.apache.org/jira/browse/DERBY-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615272#comment-13615272 ] Bryan Pendleton commented on DERBY-6069: Thanks for the updates, Christian.

[jira] [Commented] (DERBY-6069) Derby doesn't export the version number in its OSGI exported packages

[ https://issues.apache.org/jira/browse/DERBY-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614053#comment-13614053 ] Bryan Pendleton commented on DERBY-6069: I'm a bit wary about incre

[jira] [Commented] (DERBY-6075) Use modern collections in impl/sql/compile

[ https://issues.apache.org/jira/browse/DERBY-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613392#comment-13613392 ] Bryan Pendleton commented on DERBY-6075: Thanks for the follow-up and the

Re: Log indexes used by queries

*My objective* is to identify useless and extraneous indexes in the database. I would like to capture a list of indexes used by the database while it is in use by an application over a period of time. This sounds like a great tool! It would be neat if you could develop this in such a way that

Re: Connection threads sticking around

> I see that there are dozens of threads waiting on socket read() like this one: What does a tool like 'netstat' show? Are there still established network connections for each of these threads? > I have a client-side connection pool with a minimum of 10 connections, > maximum of 100, and idle

[jira] [Commented] (DERBY-6075) Use modern collections in impl/sql/compile

[ https://issues.apache.org/jira/browse/DERBY-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611497#comment-13611497 ] Bryan Pendleton commented on DERBY-6075: > I seem to be getting abou

Re: Where to look in the code to find out why XA transactions and database locks are not be cleaned up

> when I turned on the tracing, the problem goes away so that pretty much is > a good indication that there is a multi-threading problem relating to timing. Sounds like it. Bummer. You've already opened a JIRA issue, right? If not, please do so. The good thing is: - you are able to (semi-)relia

Re: Where to look in the code to find out why XA transactions and database locks are not be cleaned up

On 03/16/2013 12:08 PM, Bergquist, Brett wrote: Is there any documentation on how “SanityManager.DEBUG” or how to build so that this is applicable? Here's the docs on that: http://svn.apache.org/viewvc/db/derby/code/trunk/BUILDING.html?view=co#Customized Build Basically, put sane=t

[jira] [Commented] (DERBY-6075) Use modern collections in impl/sql/compile

[ https://issues.apache.org/jira/browse/DERBY-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13601163#comment-13601163 ] Bryan Pendleton commented on DERBY-6075: > evidence: there is no code th

Re: Is there a way to dump all the plans considered by optimizer into log?

I don't have strong feelings about whether we should document this tool in the user guides. How about in the wiki? thanks, bryan

Re: Is there a way to dump all the plans considered by optimizer into log?

I didn't find any easy way to enable it (like setting a property). So what I ended up with, was to define two stored procedures: public static void trace() { org.apache.derby.iapi.db.OptimizerTrace.setOptimizerTrace(true); } public static void printTrace() { Sys

[jira] [Commented] (DERBY-6076) Folder.gif icon missing from derby documentation website

[ https://issues.apache.org/jira/browse/DERBY-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588433#comment-13588433 ] Bryan Pendleton commented on DERBY-6076: The icons show up for me, too. Th

Re: JDBC client/server specification

I found no specification for client/server communication on your website. The Derby client/server protocols are based on DRDA: http://en.wikipedia.org/wiki/DRDA thanks, bryan

[jira] [Commented] (DERBY-6081) JDBC 4.2 setObject() and updateObject() methods throw NPE when type is null

[ https://issues.apache.org/jira/browse/DERBY-6081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582248#comment-13582248 ] Bryan Pendleton commented on DERBY-6081: Nice and clean, I lik

[jira] [Created] (DERBY-6076) Folder.gif icon missing from derby documentation website

Bryan Pendleton created DERBY-6076: -- Summary: Folder.gif icon missing from derby documentation website Key: DERBY-6076 URL: https://issues.apache.org/jira/browse/DERBY-6076 Project: Derby

[jira] [Commented] (DERBY-6075) Use modern collections in impl/sql/compile

[ https://issues.apache.org/jira/browse/DERBY-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580673#comment-13580673 ] Bryan Pendleton commented on DERBY-6075: > I suggest we switch t

[jira] [Created] (DERBY-6065) LockTable API link in the documentation is broken

Bryan Pendleton created DERBY-6065: -- Summary: LockTable API link in the documentation is broken Key: DERBY-6065 URL: https://issues.apache.org/jira/browse/DERBY-6065 Project: Derby Issue

[jira] [Commented] (DERBY-6011) Derby performs very badly (seems to deadlock and timeout) in very simple multi-threaded tests

[ https://issues.apache.org/jira/browse/DERBY-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556263#comment-13556263 ] Bryan Pendleton commented on DERBY-6011: I have no objections to the prop

[jira] [Commented] (DERBY-6011) Derby performs very badly (seems to deadlock and timeout) in very simple multi-threaded tests

[ https://issues.apache.org/jira/browse/DERBY-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551172#comment-13551172 ] Bryan Pendleton commented on DERBY-6011: If it's previous key locking,

[jira] [Commented] (DERBY-6009) Need stricter checking of ORDER BY clause in VALUES expressions

[ https://issues.apache.org/jira/browse/DERBY-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13541414#comment-13541414 ] Bryan Pendleton commented on DERBY-6009: Dag, your proposal sounds fine to m

[jira] [Commented] (DERBY-6017) IN lists with mixed types may return wrong results

[ https://issues.apache.org/jira/browse/DERBY-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537094#comment-13537094 ] Bryan Pendleton commented on DERBY-6017: +1 to the duplicates patch. I no

[jira] [Created] (DERBY-6020) Issue a clearer syntax error message for use of LIKE with a numeric column

Bryan Pendleton created DERBY-6020: -- Summary: Issue a clearer syntax error message for use of LIKE with a numeric column Key: DERBY-6020 URL: https://issues.apache.org/jira/browse/DERBY-6020 Project

[jira] [Commented] (DERBY-6017) IN lists with constants may return wrong results

[ https://issues.apache.org/jira/browse/DERBY-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536050#comment-13536050 ] Bryan Pendleton commented on DERBY-6017: A little bit of quick searching conf

[jira] [Commented] (DERBY-6017) IN lists with constants may return wrong results

[ https://issues.apache.org/jira/browse/DERBY-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536036#comment-13536036 ] Bryan Pendleton commented on DERBY-6017: Thank you Knut Anders for digging

[jira] [Commented] (DERBY-6017) IN lists with constants may return wrong results

[ https://issues.apache.org/jira/browse/DERBY-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535049#comment-13535049 ] Bryan Pendleton commented on DERBY-6017: A very clear description, and a

[jira] [Commented] (DERBY-6008) Allow ORDER BY and FETCH/OFFSET in set operands

[ https://issues.apache.org/jira/browse/DERBY-6008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531874#comment-13531874 ] Bryan Pendleton commented on DERBY-6008: > I should avoid the FIXME word,

[jira] [Commented] (DERBY-6008) Allow ORDER BY and FETCH/OFFSET in set operands

[ https://issues.apache.org/jira/browse/DERBY-6008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13531077#comment-13531077 ] Bryan Pendleton commented on DERBY-6008: I'm generally comfortable

[jira] [Updated] (DERBY-6009) Need stricter checking of ORDER BY clause in VALUES expressions

[ https://issues.apache.org/jira/browse/DERBY-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Pendleton updated DERBY-6009: --- Summary: Need stricter checking of ORDER BY clause in VALUES expressions (was: Need

<    10   11   12   13   14   15   16   17   18   19   >