Re: [VOTE] 10.5.3.0 release

Rick Hillegas wrote: Please test-drive the 10.5.3.0 candidate, then vote on whether to accept it as a Derby release. The candidate lives at: http://people.apache.org/~rhillegas/10.5.3.0/ The polls close at 5:00 pm San Francisco time on Thursday, August 20. 10.5.3.0 is a bug-fix vehicle,

Re: [VOTE] Ole Solberg as a committer

Rick Hillegas wrote: Please vote on whether we should make Ole Solberg a committer. The vote closes at 5:00 pm San Francisco time on Thursday June 4. For 4+ years Ole has been a significant contributor to Derby. We all rely heavily on Ole's failure analysis and on the tests and testing

Re: [VOTE] 10.5.1.1 release candidate

+1 On 04/15/09 04:35, Myrna van Lunteren wrote: Dear all, The blockers found during the test-and-vote period for 10.5 RC1 have been fixed... Please test and vote on the second 10.5 release candidate, 10.5.1.1 (revision 764942), available at:

Re: Replication

Hi Mike, Currently the replication functionality is not a pluggable module but is rather strongly linked with the store layer. For example LogToFile has been actually modified to catch the log records and store them in the log buffer in addition to storing them on the master. If you are

Re: DaemonFactory vs Threads in derby

Dag H. Wanvik wrote: V Narayanan [EMAIL PROTECTED] writes: Hi, I am working on the LogShipper design for the Replication work. During this course of that work I am at a place where I need to design a seperate thread Not sure if it's appropriate in this case, but you may want

Re: [jira] Commented: (DERBY-3064) Implement the LogShipper that will enable the shipping of Log records from the master to the slave

Jørgen Løland (JIRA) wrote: [ https://issues.apache.org/jira/browse/DERBY-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529838 ] Jørgen Løland commented on DERBY-3064: -- Does this mean atleast in the case of

DaemonFactory vs Threads in derby

Hi, I am working on the LogShipper design for the Replication work. During this course of that work I am at a place where I need to design a seperate thread that ships log chunks from the master to the slave. I initially decided on designing this by using the derby DaemonFactory. But I realize

Re: [VOTE] Dyre Tjeldvoll as a committer

Rick Hillegas wrote: Please vote on whether we should make Dyre Tjeldvoll a committer. +1 Narayanan

Re: [VOTE] Øystein Grøvlen as a commi tter

+1 Narayanan Rick Hillegas wrote: Please vote on whether we should make Øystein Grøvlen a committer. The vote will close at 5:00 pm San Francisco time on Tuesday August 28. Since 2005, Øystein has been submitting patches, fielding questions on the Derby mailing lists, and mentoring

Re: problem while attaching a file to JIRA

Dag H. Wanvik wrote: I get the following when I try to attach a file to a JIRA. Does anyone know how to resolve this? I see it also. I don't know what is the issue. Dag V Narayanan [EMAIL PROTECTED] writes: Hi Dag, Thank you for the reply. Yes seems like a problem with JIRA. I

[patch] Derby-2921 (sending as an email since JIRA is not allowing attachment to the issue)

Hi, I have been working on Derby-2921( Replication: Add a network service that connects the master and slave Derby instances ) and have developed a preliminary patch for it. I have not been able to attach it to JIRA the whole of the afternoon today hence I am sending it as an attachment

problem while attaching a file to JIRA

Hi, I get the following when I try to attach a file to a JIRA. Does anyone know how to resolve this? A system error has occurred. If this problem persists - please notify your JIRA administrator of this problem. If you are an administrator, please try submitting this problem via the

Re: DERBY-581 and OLAP operations

Hi, Welcome to derby! If you are confident of the issue you want to work on feel free to start working on a JIRA issue. But if you think you need to start with some simple issues and then move on to the issues you think are a little bit more complicated this page contains lot of

Re: Compile failing: can't find org.apache.xpath.*

Including the xalan files in your classpath might work with 1.5 or later. But 1.4 has its own embedded xalan that needs to be overridden by copying the xalan files to jre/lib/endorsed of your 1.4 installation. There was a discussion regarding this recently for running xml tests. Thought it

Re: Compile failing: can't find org.apache.xpath.*

Found the nabble thread for this http://www.nabble.com/running-the-XML-tests-tf3531838.html#a9858817 Narayanan [EMAIL PROTECTED] wrote: Including the xalan files in your classpath might work with 1.5 or later. But 1.4 has its own embedded xalan that needs to be overridden by copying the

[JDBC] [LOB] Behavior of Streams returned from LOB (Related to DERBY-2763 and 2764)

Hi, The following is a list of the possible solutions for DERBY-2763 and DERBY-2764. I have already commented the below list of points on DERBY-2763. But thought it would be better to send it as an email also. DERBY-2763 - In the Network Client InputStream returned using

Re: 10.3 release coming up...fast!

Myrna van Lunteren wrote: Hi! We have now about 7 days before the code complete date of 6/1/07! I now want to talk about 3 things: 1. code complete 6/1 2. regression bugs 3. release testing 1. code complete 6/1 For those of you who plan to have functionality fixed/completed

Re: Blob/Clob Stored procedures with embedded and JSR169

Thank you for doing this. Narayanan Myrna van Lunteren wrote On 05/09/07 22:40,: Thx for your reply. I'll log a separate bug for the failure with the upgrade tests and add the stack trace. It's probably the same as the original trouble. Apparently, junit grabs hold of the actual fixtures in

Re: Blob/Clob Stored procedures with embedded and JSR169

Hi, failures of these tests in weme6.1 were fixed as part of DERBY-2427 1. re *lobStoredProcedureTest.suite: why is this test using TestConfiguration.defaultSuite, when it is apparently only a test for client? This test does not need to run in the embedded mode. They just need to test the LOB

Re: svn commit: r535319 - in /db/derby/code/trunk/java/client/org/apache/derby/client: am/Clob.java am/ClobLocatorInputStream.java am/ClobLocatorOutputStream.java am/ClobLocatorReader.java am/ClobLoca

Myrna van Lunteren wrote On 05/08/07 04:21,: On 5/4/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Author: rhillegas Date: Fri May 4 09:32:39 2007 New Revision: 535319 URL: http://svn.apache.org/viewvc?view=revrev=535319 Log: DERBY-2604: Commit Naryayan's ClobLocatorWork_v1.diff, adding

Re: Debug tracing

Hi Dyre, Does this link http://wiki.apache.org/db-derby/ProtocolDebuggingTips seem to be of relevance here? Narayanan [EMAIL PROTECTED] wrote On 05/03/07 15:24,: During my dives into the Derby source I have stumbled across SanityManager.DEBUG_ON() which allows you to turn on specific

Re: is anyone looking at new import/export tinderbox errors that look like they started with checkin for DERBY-2193 or DERBY-2444?

Blob.getBinaryStream(long pos, long length) and Clob.getCharacterStream(long pos, long length) in the Network Client Patch contributed by V. Narayanan. Ujava/engine/org/apache/derby/impl/load/Import.java Ujava/engine/org/apache

Re: running the XML tests

Hi, This issue seems to contain some information related to your question https://issues.apache.org/jira/browse/DERBY-563 Narayanan Rick Hillegas wrote On 04/05/07 19:39,: I'd like to setup my environment so that our XML tests run. I'm having a hard time finding instructions for how to do

Re: running the XML tests

Hi, I am lost here because placing the jar files in the jre/lib/ext is the standard override mechanism. The information here http://xml.apache.org/xalan-j/faq.html#faq-N100D6 seems to concur with that. Narayanan Rick Hillegas wrote On 04/05/07 20:37,: Thanks Bryan and Narayanan, I have

Re: running the XML tests

I did not read it properly I read the information in the link as java-home\lib\endorsed directory not jre/ext/lib. Sorry about the mistake. Narayanan V Narayanan wrote On 04/05/07 20:52,: Hi, I am lost here because placing the jar files in the jre/lib/ext is the standard override mechanism

Re: running the XML tests

Army wrote On 04/05/07 20:56,: Rick Hillegas wrote: I have downloaded xalan 2.7.0 (that seems to be the latest release available from the xalan site). I copied the four jar files mentioned by Bryan into the jre/lib/ext directory of my JDK 1.4. This did slightly change the output of the

Re: Feedback on wiki page http://wiki.apache.org/db-derby/BuiltInLanguageBasedOrderingDERBY-1478

Excellent work of organizing everything so neatly. As much as I am a passive reader of the language related work I really appreciate your efforts in organizing the discussions. Narayanan Mamta Satoor wrote On 04/03/07 11:35,: Hi, I have created a wiki page for DERBY-1478 : Add built in

Re: [jira] Commented: (DERBY-2444) Implement not implemented methods Blob.getBinaryStream(long pos, long length) and Clob. getCharacterStream(long pos, long length) in the Network Client

Knut Anders Hatlen (JIRA) wrote: [ https://issues.apache.org/jira/browse/DERBY-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484359 ] Knut Anders Hatlen commented on DERBY-2444: --- Thanks for the updated patch,

[upgrade Tests] Reusing existing junit test in Uprgade test

Hi, I am writing tests to test the StoredProcedures used in locator implementation of LOB related JDBC methods. The Stored procedures are created when the database version is 10.3 (or upon hard(full) upgrade to 10.3). Tests for the Stored Procedure exist in the form of

Re: Running test suites and interpreting results

the jdk16 variable and run the jdbc4 suite alone. You can do this by java org.apache.derbyTesting.functionTests.harness.RunSuite jdbc4 and check if the failures occur. If they don't then you can continue with derbyall. Hope this helps! :-) Narayanan V Narayanan wrote: Hi Jeffrey, From what

Re: Running test suites and interpreting results

Jeffrey Clary wrote: I didn't attach them before because of their size, but here you go. Thank you for attaching it. I checked for the failures in the jdbc4 suite and this gives you the clue java.lang.NoClassDefFoundError:

Re: [upgrade Tests] Reusing existing junit test in Uprgade test

Daniel John Debrunner wrote: V Narayanan wrote: Hi, I am writing tests to test the StoredProcedures used in locator implementation of LOB related JDBC methods. The Stored procedures are created when the database version is 10.3 (or upon hard(full) upgrade to 10.3). Tests for the Stored

Re: Running test suites and interpreting results

Hi Jeffrey, From what you have pasted you seem to be running with 1.6. While doing a build of the code base can you check if you have set the jdk16 property in ant.properties file? If you have not done so can you do it and run derbyall again and check if you are getting the failures you have

Re: Running test suites and interpreting results

! :-) Narayanan V Narayanan wrote: Hi Jeffrey, From what you have pasted you seem to be running with 1.6. While doing a build of the code base can you check if you have set the jdk16 property in ant.properties file? If you have not done so can you do it and run derbyall again and check if you

1 Failure when I run jdbcapi._Suite

Hi, I get the following error when I do java junit.textui.TestRunner org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite 1) prepStmtMetaData(org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCHarnessJavaTest)java.lang.ClassNotFoundException:

Re: [VOTE] Dag Wanvik as a committer

Rick Hillegas wrote: Please vote on whether we should make Dag Wanvik a Derby committer. The vote will close at 5:00 pm San Francisco time on Monday March 19. +1

Difference in behaviour of Derby client and Embedded driver when doing a updateClob and a updateBlob

Hi, I was working on implementing updateClob/updateBlob methods on the network client when I noticed the following. 1) updateClob on a CHAR/VARCHAR/LONG VARCHAR column throws an exception on the Embedded Driver but not on the NetworkClient 2) updateBlob works on a CHAR/VARCHAR/LONG VARCHAR

Re: Difference in behaviour of Derby client and Embedded driver when doing a updateClob and a updateBlob

Knut Anders Hatlen wrote: V Narayanan [EMAIL PROTECTED] writes: Hi, I was working on implementing updateClob/updateBlob methods on the network client when I noticed the following. 1) updateClob on a CHAR/VARCHAR/LONG VARCHAR column throws an exception on the Embedded Driver

Re: [VOTE] Accept NetworkServer system tests contributed by IBM

Jean T. Anderson wrote: As required by the ASF ip-clearance process in the Incubator [1], please vote to accept the NetworkServer system tests contributed by IBM that are attached to the following Jira issue: https://issues.apache.org/jira/browse/DERBY-2248 I'll close this vote on February

[LOB] Request for Advice in Implementing the stored procedures called by the LOB related JDBC methods.

Hi, I am working on implementing the Stored procedures, related to adding support to retrieving lobs from Network Server by locator rather than by materializing the LOB. The network client will request LOB columns to be sent as LOB Locators instead of data value bytes. Since the client no

Re: [VOTE] Knut Anders Hatlen as committer

+1 Narayanan - Original Message - From: David Van Couvering [EMAIL PROTECTED] Date: Wednesday, February 8, 2006 11:51 pm Subject: [VOTE] Knut Anders Hatlen as committer To: Derby Development derby-dev@db.apache.org This vote is for adding Knut Anders Hatlen as a committer to Derby.

Re: [jira] Commented: (DERBY-796) jdbc 4.0 specific Blob and Clob method support

Hi, Will the setBinaryStreamInternal method be raising an exception if the length variable doesn't fit inside an integer. Or is SetBinaryStreamInternal and the related classes being modified to work with the length variable as a long type. thanx Narayanan Sunitha Kambhampati (JIRA) wrote:

Re: [VOTE] Rick Hillegas as a committer

+1 David W. Van Couvering wrote: This vote is for establishing Rick Hillegas as a committer for Derby. Please vote +1 if you approve of Rick as a committer.

Re: [jira] Commented: (DERBY-768) Build doesnt fail inspite of presence of a bug in JDBC4.0 specific classes and setting proceed=false

Hi Rick, I am sending this mail on the list because JIRA is down. I observe this problem when I run ant with the -quiet flag. But when I run it without the -quiet flag I observe the following. compile_jdbc4_target: [exec] Buildfile:

Re: [jira] Commented: (DERBY-796) jdbc 4.0 specific Blob and Clob method support

Hi Rick, I am looking in to the failure in lobStreams.java. The failure in jdbc4 is due to the NetworkServer not being started. The tests expect the NetworkServer to be up. I will update the testcase to start the NetworkServer from the test itself. thanx, V.Narayanan Rick Hillegas (JIRA)

When does a PreparedStatement become invalid in derby?

Hi, I am working on StatementEventListeners as part of providing JDBC4.0 support to derby. The driver calls the statementErrorOccurred method on all StatementEventListeners registered on the connection when it detects that a PreparedStatement is invalid. One situation when this

Re: IBM Java 5.0 class file for test harness

for this and attach it to that? thanx V.Narayanan Dag H. Wanvik wrote: Hi, V == V Narayanan [EMAIL PROTECTED] wrote: V can you please confirm that the compilation was done with jdk16 V variable in ant.properties pointing to mustang home. The V ClientPooledConnection40.java gets compiled only

Re: [jira] Commented: (DERBY-587) Providing JDBC 4.0 support for derby

Hi, Thanx for the help with the icla Jean. Thank you Satheesh and Rick for guiding me through the various details of the patch. Thanx to everyone for the reviews and the comments. Narayanan Satheesh Bandaram (JIRA) wrote: [

Re: [jira] Updated: (DERBY-587) Providing JDBC 4.0 support for derby

Hi, The jdk1.6 dependency is optional in the patch. a) If the jdk16 variable is mentioned in the ant.properties file then the jdbc4.0 classes are compiled b) If the ant.properties does not contain the jdk16 variable the compilation would proceed the usual way. I see that I have not

Re: [jira] Updated: (DERBY-353) It is desirable to have IDENTITY_VAL_LOCAL() function return last recent user specified value or system generated value for BY DEFAULT identity columns.

Hi Satheesh, Thanx for committing! I just wanted to point out that this patch also fixes DERBY-439. This was the test case pointed out which was returning null. This returns the correct value now. ij connect 'jdbc:derby:mydb;create=true'; ij CREATE TABLE MYTABLE ( MYTABLE_ID BIGINT NOT

Re: fix to bug 353

Hi, I have posted a new patch for DERBY-353 following Rick's directions. Pls review the patch and give me your comments. thanx V.Narayanan Satheesh Bandaram wrote: It doesn't look like a new patch has been posted, following Rick's comments. Narayanan seems to have said he would update the

Re: request for developer status

: On Aug 10, 2005, at 9:25 PM, V Narayanan wrote: Pls grant me developer status so that I can assign bugs to myself. thanx V.Narayanan You appear to have two usernames in JIRA: narayanan and narayananv. Which userid would you like me to add to the derby-developers group? And would you like me

request for developer status

Pls grant me developer status so that I can assign bugs to myself. thanx V.Narayanan

jdbc4.0 implementation plan

1) build a stub foundation into which we can plug additional features incrementally and in parallel steps in doing this a) create a seperate package org.apache.derby.impl.jdbc4 b) extend classes in the org.apache.derby.impl.jdbc package c) provide

Re:[Patch]Derby-105

Hi, I did try out the query with the comment and it led to the following output ij -- an insert statement insert into table2 select * from table1; 12 --s executed considering the approach I am using to solve the problem I can resolve this by further parsing of the query in addition to

Unable to open page where derby issues are maintained

Hi, I was unable to access the following link http://issues.apache.org/jira/browse/DERBY . Can anyone please tell me if it because the server has gone down due to some issue or it is because the server is shutdown for regular maintanence. Thanx V.Narayanan