[jira] Updated: (DERBY-23) just booting jdbc driver and shutting down seem to leak memory

[ http://issues.apache.org/jira/browse/DERBY-23?page=all ] Knut Anders Hatlen updated DERBY-23: Attachment: DERBY-23-with_comments.diff Attached patch with comments where appropriate. just booting jdbc driver and shutting down seem to leak memory

[jira] Reopened: (DERBY-504) SELECT DISTINCT returns duplicates when selecting from subselects

[ http://issues.apache.org/jira/browse/DERBY-504?page=all ] Knut Anders Hatlen reopened DERBY-504: -- Reopen the bug so the fix can be included in 10.1.2. Since the bug was reported on derby-user before 10.1.1 was released, I think it should be

[jira] Updated: (DERBY-504) SELECT DISTINCT returns duplicates when selecting from subselects

[ http://issues.apache.org/jira/browse/DERBY-504?page=all ] Knut Anders Hatlen updated DERBY-504: - Fix Version: 10.1.2.0 (was: 10.2.0.0) Version: 10.1.2.0 (was: 10.2.0.0) Changed fix version.

Re: 10.1.2 Release status page

Daniel John Debrunner wrote: Francois Orsini wrote: Nightly builds should only be posted if regression tests have passed IMHO. I disagree, a nightly build is use at your own risk. Even if one test fails the jar may still work and allow anyone to test other areas. I think the nightly

[jira] Commented: (DERBY-577) Test harness should not change the user.dir property , it is meant for infomative purpose only.

[ http://issues.apache.org/jira/browse/DERBY-577?page=comments#action_12329982 ] Thomas Lecavelier commented on DERBY-577: - Hi Suresh, I follow the references about userDirName, it appears it's build from System.getProperties() and I see nowhere

[jira] Created: (DERBY-579) Query timeout set for one statement may affect other statements with the same SQL string

Query timeout set for one statement may affect other statements with the same SQL string Key: DERBY-579 URL: http://issues.apache.org/jira/browse/DERBY-579 Project: Derby Type:

Re: [jira] Updated: (DERBY-504) SELECT DISTINCT returns duplicates when selecting from subselects

Knut Anders Hatlen (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-504?page=all ] Knut Anders Hatlen updated DERBY-504: - Fix Version: 10.1.2.0 (was: 10.2.0.0) Version: 10.1.2.0

[jira] Updated: (DERBY-579) Query timeout set for one statement may affect other statements with the same SQL string

[ http://issues.apache.org/jira/browse/DERBY-579?page=all ] Oyvind Bakksjo updated DERBY-579: - Attachment: DERBY-579.svn.status Query timeout set for one statement may affect other statements with the same SQL string

[jira] Updated: (DERBY-579) Query timeout set for one statement may affect other statements with the same SQL string

[ http://issues.apache.org/jira/browse/DERBY-579?page=all ] Oyvind Bakksjo updated DERBY-579: - Attachment: DERBY-579.svn.diff This patch fixes the bug as proposed by Dan Debrunner (pass the timeout into the execute method of

[jira] Closed: (DERBY-574) Per JDBC connection timeouts are incorrectly set on org.apache.derby.iapi.sql.PreparedStatement which represents a shared plan.

[ http://issues.apache.org/jira/browse/DERBY-574?page=all ] Oyvind Bakksjo closed DERBY-574: Fix Version: (was: 10.2.0.0) Resolution: Duplicate Per JDBC connection timeouts are incorrectly set on

[jira] Updated: (DERBY-504) SELECT DISTINCT returns duplicates when selecting from subselects

[ http://issues.apache.org/jira/browse/DERBY-504?page=all ] Knut Anders Hatlen updated DERBY-504: - Fix Version: 10.2.0.0 SELECT DISTINCT returns duplicates when selecting from subselects

[jira] Commented: (DERBY-428) NetworkClient PreparedStatement.executeBatch() hangs if batch is too large (ArrayIndexOutOfBoundsException in Network Server)

[ http://issues.apache.org/jira/browse/DERBY-428?page=comments#action_12330002 ] Gregory W. Inns commented on DERBY-428: --- We're getting one similar to this one, but only sporadically. Does anyone know a workaround for it? NetworkClient

Re: [jira] Updated: (DERBY-374) Invalid URL with Derby Client when connecting to Network Server causes protocol exception.

Kathey, I checked with network server trace on and for the URLs below, the server does not reach till ACCRDB response to send a RDBAFLRM. * 'jdbc:derby://localhost:1527/sample:create=true' * 'jdbc:derby://localhost:1527/C:/myDBs/sample;create=true' These URLs cause a NullPointerException in the

[jira] Commented: (DERBY-573) Provider support for optimizer overrides in Derby.

[ http://issues.apache.org/jira/browse/DERBY-573?page=comments#action_12330020 ] Satheesh Bandaram commented on DERBY-573: - It should be possible to enhance current Derby RunTimeStatistics mechanism to display user specified optimizer directives

Re: [jira] Updated: (DERBY-374) Invalid URL with Derby Client when connecting to Network Server causes protocol exception.

Deepa Remesh wrote: I am using RDBAFLRM for failure to find a suitable driver. Is this okay or is there any specific message type that must be used in such a case? I think that is the best we can do from the server side as we cannot send a full SQLCARD in this case. I am not sure what

[jira] Commented: (DERBY-573) Provider support for optimizer overrides in Derby.

[ http://issues.apache.org/jira/browse/DERBY-573?page=comments#action_12330031 ] Mamta A. Satoor commented on DERBY-573: --- I can look into modifying the RunTimeStatistics to indicate that user overrides are being used. Also, I will see how parser can

Re: Modular build, was: VOTE: Approach for sharing code

There are now three cloning proposals for handling shared code: 1) Hand cloning by the developer as is done today. 2) Build-time cloning. 3) Release-time cloning (David's latest proposal). All of these cloning approaches address Dan's problem case: a client and server at diffferent rev

[jira] Created: (DERBY-581) Modify SQL to skip N rows of the result and return the next M rows

Modify SQL to skip N rows of the result and return the next M rows -- Key: DERBY-581 URL: http://issues.apache.org/jira/browse/DERBY-581 Project: Derby Type: New Feature Components: Unknown

[Fwd: Re: additional drda datatypes]

This issue is moving forward on a geologic time scale. Far enough forward that I have been asked: who can champion this issue in other (that is, not Sun) companies? Can one of the IBM folks find an IBM champion for this issue? Thanks, -Rick ---BeginMessage--- Rick, Rick the working group

[PATCH] jdk15 canons for 3 tests for 10.0 branch (ref commit # 149488)

Hi, Attached is a patch that adds 3 jdk15 canons to the DerbyNet dir for the 10.0 branch. The change is in essence the same as for commit 149488 to the main branch, but 2of the3 tests are a little different, so a backport will be a little awkward. If someone can add this to the 10.0 branch?

Re: [PATCH] jdk15 canons for 3 tests for 10.0 branch (ref commit # 149488)

On 9/20/05, Myrna van Lunteren [EMAIL PROTECTED] wrote: Attached is a patch that adds 3 jdk15 canons to the DerbyNet dir for the 10.0 branch. Committed revision 290576. andrew

[jira] Updated: (DERBY-566) Doc bug for saving ij output to a file

[ http://issues.apache.org/jira/browse/DERBY-566?page=all ] Andrew McIntyre updated DERBY-566: -- Fix Version: 10.1.1.1 (was: 10.1.2.0) (was: 10.1.1.0) Version: 10.1.1.0 Doc bug for saving ij output to a

[jira] Updated: (DERBY-566) Doc bug for saving ij output to a file

[ http://issues.apache.org/jira/browse/DERBY-566?page=all ] Andrew McIntyre updated DERBY-566: -- Fix Version: 10.2.0.0 10.1.2.0 Doc bug for saving ij output to a file -- Key: DERBY-566

[jira] Commented: (DERBY-149) Server hang when invalid string is bound to datetime columns.

[ http://issues.apache.org/jira/browse/DERBY-149?page=comments#action_12330055 ] Kathey Marsden commented on DERBY-149: -- Looking at this problem, I see that other types of errors, such as insert of a null value into a not null column seem to work ok.

Re: 10.1.2 Release status page

Andrew McIntyre wrote: Hmm, this would be my fault. The version should have been bumped after each release and I neglected to do that immediately after the last release. Also, I merged the issues with 10.1.1.1 FixIns to 10.1.2.0. While that was a probably a good idea, in order to target

[jira] Updated: (DERBY-562) Derby incorrectly throws Exception when streaming to BLOB field

[ http://issues.apache.org/jira/browse/DERBY-562?page=all ] Sunitha Kambhampati updated DERBY-562: -- Attachment: Derby562.stat.txt Derby incorrectly throws Exception when streaming to BLOB field

Re: Modular build, was: VOTE: Approach for sharing code

David W. Van Couvering wrote: This proposal was based on the assumption that our common code would *never* be exposed to the outside world. I also never claimed that we should apply this solution to third-party components. That's a fish I don't think we need to fry right now. Although I

Re: Modular build, was: VOTE: Approach for sharing code

Daniel John Debrunner wrote: Jeremy Boynes wrote: Think of the carnage if it was java_14208_b13.sql_300.Connection It's actually instructive to look how Java solves this: - The interface is kept upwards compatible, by following rules such as only new methods/fields etc. Then to look at

Re: Modular build, was: VOTE: Approach for sharing code

Thanks for writing up a proposed solution, I was getting a little tired of putting up targets for others to shoot down. I agree with this wholeheartedly this was what I have wanted to do (although perhaps not as well communicated and there are some details here that are new and which seem