[jira] Reopened: (DERBY-1078) Be able to build Derby when JAVA_HOME is set 1.6

[ http://issues.apache.org/jira/browse/DERBY-1078?page=all ] Andrew McIntyre reopened DERBY-1078: Assign To: Andrew McIntyre Reopening this issue due to ij,jj issue with IBM JDK 1.3.1. See following comment. Be able to build Derby when

[jira] Commented: (DERBY-1078) Be able to build Derby when JAVA_HOME is set 1.6

[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12377524 ] Andrew McIntyre commented on DERBY-1078: Committed revision 399164. This fixes a couple more tests under jdk131, specifically stress.multi and dataSourcePermissions

Re: JUnit documentation (was: [jira] Updated: (DERBY-578) Grouped select from temporary table raises null pointer exception in byte code generator)

Manish Khettry (JIRA) wrote: [ http://issues.apache.org/jira/browse/DERBY-578?page=all ] Manish Khettry updated DERBY-578: - Attachment: 578.diff.txt The problem is simple enough-- we didn't have a conglomerate name for temporary tables. I fixed the

[jira] Updated: (DERBY-1234) Verify that we raise SQLException when calling methods on closed java.sql objects

[ http://issues.apache.org/jira/browse/DERBY-1234?page=all ] Knut Anders Hatlen updated DERBY-1234: -- Attachment: derby-1234-part4.diff derby-1234-part4.stat New patch (part4) which fixes the issues in EmbedConnection: 1) New

[jira] Commented: (DERBY-1261) Two triggers on same table cause ERROR 54038: Maximum depth of nested triggers was exceeded.

[ http://issues.apache.org/jira/browse/DERBY-1261?page=comments#action_12377531 ] Øystein Grøvlen commented on DERBY-1261: I am not quite sure what the definition of a recursive trigger is, and I did not find any definition of that in the

[jira] Commented: (DERBY-1255) Implement new JDBC4 methods for creating empty LOBs in the embedded client

[ http://issues.apache.org/jira/browse/DERBY-1255?page=comments#action_12377537 ] Kristian Waagan commented on DERBY-1255: create[BC]lob is missing in LogicalConnection on the client side as well. Should be easy to implement there, as the methods

Regression Test Failure! - TinderBox_Derby 399165 - Sun DBTG

[Auto-generated mail] *TinderBox_Derby* 399165/2006-05-03 08:22:26 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* 1654653 1 138.84% SunOS-5.10_i86pc-i386 Details in

Regression Test Failure! - Derby 398984 - Sun DBTG

[Auto-generated mail] *Derby* 398984/2006-05-02 19:46:07 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.6* 130668538 0 105.57% SunOS-5.10_i86pc-i386 Details in

Re: LargeCodegen test fails with derbyclient while running largeData test suite

Ramandeep Kaur [EMAIL PROTECTED] writes: Now it looks like it could be a diff problem. Any idea??? Whenever I find it difficult to understand the diff I use tkdiff (or a similar tool) that shows the master and the output side by side, highlighting any differences. That usually makes it easy to

Re: [VOTE] Halley Pacheco de Oliveira as committer

Jean T. Anderson [EMAIL PROTECTED] writes: This vote is for establishing Halley Pacheco de Oliveira as a documentation committer for Derby. Halley has translated the Derby Getting Started Guide and the Derby Reference to Brazilian Portuguese (DERBY-780, DERBY-1138) and tells me the Derby

[jira] Commented: (DERBY-1181) Implement missing JDBC4 methods discovered by DERBY-1146

[ http://issues.apache.org/jira/browse/DERBY-1181?page=comments#action_12377543 ] Kristian Waagan commented on DERBY-1181: The following embedded methods need implementations: a) DERBY-1145 : java.sql.Blob.free() b) ?:

[jira] Resolved: (DERBY-1180) Add vacuous implementations of missing JDBC4 methods

[ http://issues.apache.org/jira/browse/DERBY-1180?page=all ] Knut Anders Hatlen resolved DERBY-1180: --- Fix Version: 10.2.0.0 Resolution: Fixed Deleting

[jira] Created: (DERBY-1277) Call to rs.isLast() may cause rs.getXXX() return values from the last row instead of the current row in scrollable updatable resultsets

Call to rs.isLast() may cause rs.getXXX() return values from the last row instead of the current row in scrollable updatable resultsets --- Key: DERBY-1277

[jira] Updated: (DERBY-941) Add JDBC4 support for Statement Events

[ http://issues.apache.org/jira/browse/DERBY-941?page=all ] V.Narayanan updated DERBY-941: -- Attachment: statementeventlisteners_client_v4.diff statementeventlisteners_client_v4.stat Resolving earlier conflicts with 1235 and 1180 and

[jira] Assigned: (DERBY-1277) Call to rs.isLast() may cause rs.getXXX() return values from the last row instead of the current row in scrollable updatable resultsets

[ http://issues.apache.org/jira/browse/DERBY-1277?page=all ] Andreas Korneliussen reassigned DERBY-1277: --- Assign To: Andreas Korneliussen Call to rs.isLast() may cause rs.getXXX() return values from the last row instead of the current row

[jira] Commented: (DERBY-955) Get derbyall on jdk1.6

[ http://issues.apache.org/jira/browse/DERBY-955?page=comments#action_12377573 ] Rick Hillegas commented on DERBY-955: - Committed bug955_blobclob4BLOB.diff at subversion revision 399293. Derbyall runs cleanly on jdk1.4 modulo the wisconsin diffs. Get

Re: [WWD] Review of Final Chapters (5 and 6)

Jean T. Anderson wrote: Stanley Bradbury wrote: ... snip And now onto you question: A better name for DerbyInstruction here are some off-the-top (if not off-the-wall) suggestions (I like DerbyHowTo as well): DerbyCookbook - CookingWithDerby - DerbyRecipes - DerbyRecipebook

[jira] Commented: (DERBY-846) Internationalze NetAgent to NetDatabaseMetadata40 in org.apache.derby.client.net

[ http://issues.apache.org/jira/browse/DERBY-846?page=comments#action_12377584 ] Andreas Korneliussen commented on DERBY-846: In my review comments posted on derbydev, I commented on the error message: ERROR 08004: Connection authorization

Regression Test Failure! - TinderBox_Derby 399265 - Sun DBTG

[Auto-generated mail] *TinderBox_Derby* 399265/2006-05-03 13:32:28 CEST *derbyall* Failed TestsOK Skip Duration Platform --- *Jvm: 1.5* 1654653 1 144.60% SunOS-5.10_i86pc-i386 Details in

[jira] Commented: (DERBY-846) Internationalze NetAgent to NetDatabaseMetadata40 in org.apache.derby.client.net

[ http://issues.apache.org/jira/browse/DERBY-846?page=comments#action_12377594 ] David Van Couvering commented on DERBY-846: --- Thanks, Andreas, I'll fix this. Internationalze NetAgent to NetDatabaseMetadata40 in org.apache.derby.client.net

[jira] Resolved: (DERBY-846) Internationalze NetAgent to NetDatabaseMetadata40 in org.apache.derby.client.net

[ http://issues.apache.org/jira/browse/DERBY-846?page=all ] David Van Couvering resolved DERBY-846: --- Resolution: Fixed Checked in revisions 399078 and 399351 (missing master file) Internationalze NetAgent to NetDatabaseMetadata40 in

[jira] Resolved: (DERBY-850) Internationalize all classes in java/client/org/apache/derby/jdbc

[ http://issues.apache.org/jira/browse/DERBY-850?page=all ] David Van Couvering resolved DERBY-850: --- Resolution: Fixed Committed revision 399352. Passes derbynetclientmats Internationalize all classes in java/client/org/apache/derby/jdbc

Re: [jira] Commented: (DERBY-514) Integrate upgrade tests into test suite

On 5/1/06, Deepa Remesh (JIRA) derby-dev@db.apache.org wrote: * If someone updates the derbyTesting.jar.path in ant.properties file and rebuilds without running clobber, the Upgrade_10_1_10_2_app.properties will not get updated since it gets updated depending on output of available task. I

Re: LargeCodegen test fails with derbyclient while running largeData test suite

Ramandeep Kaur wrote: Hi, I ran largeCodeGen as following: java -Dverbose=true -Djvmflags=-mx512M -ms512M -Dframework=DerbyNetClient org.apache.derbyTesting.functionTests.harness.RunTest lang/largeCodeGen.java With the above, I did NOT get usual error which was *** Start: largeCodeGen

[jira] Commented: (DERBY-1078) Be able to build Derby when JAVA_HOME is set 1.6

[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12377601 ] Andrew McIntyre commented on DERBY-1078: If I qualify the inherit references to tokenImage in both ij.java and SQLParser.java by adding their classnames (e.g. in

[jira] Created: (DERBY-1278) hang on shutdown after getting both DriverManager and DataSource connections with security mechanism on zOS and ibm15 and networkserver client

hang on shutdown after getting both DriverManager and DataSource connections with security mechanism on zOS and ibm15 and networkserver client --

[jira] Reopened: (DERBY-387) SimpleNetworkClientSample.java network server example has an error which causes it to fail

[ http://issues.apache.org/jira/browse/DERBY-387?page=all ] Andrew McIntyre reopened DERBY-387: --- Reopening to merge to 10.1 SimpleNetworkClientSample.java network server example has an error which causes it to fail

[jira] Resolved: (DERBY-387) SimpleNetworkClientSample.java network server example has an error which causes it to fail

[ http://issues.apache.org/jira/browse/DERBY-387?page=all ] Andrew McIntyre resolved DERBY-387: --- Fix Version: 10.1.3.0 10.1.2.4 Resolution: Fixed Committed to 10.1 branch with revision 399370.

[jira] Commented: (DERBY-1078) Be able to build Derby when JAVA_HOME is set 1.6

[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12377609 ] Rick Hillegas commented on DERBY-1078: -- Hi Andrew, You can use the ant replace task for this. Thanks for digging into this problem! Be able to build Derby when

[jira] Updated: (DERBY-1078) Be able to build Derby when JAVA_HOME is set 1.6

[ http://issues.apache.org/jira/browse/DERBY-1078?page=all ] Andrew McIntyre updated DERBY-1078: --- Attachment: derby-1078_part3.diff Attaching patch3 to resolve the problem with the parsers in IBM JDK 1.3.1 mentioned above. I will commit this shortly

[jira] Created: (DERBY-1279) Bad column name in DatabaseMetaData.getColumns()

Bad column name in DatabaseMetaData.getColumns() Key: DERBY-1279 URL: http://issues.apache.org/jira/browse/DERBY-1279 Project: Derby Type: Bug Components: JDBC Versions: 10.2.0.0 Reporter: Rick

[jira] Commented: (DERBY-1266) Client: Attempted deleteRow or updateRow while on insert row gives wrong error message

[ http://issues.apache.org/jira/browse/DERBY-1266?page=comments#action_12377613 ] David Van Couvering commented on DERBY-1266: Hi, Dag. There is an existing message XJ120.S=This method cannot be invoked while the cursor is on the insert row,

[jira] Created: (DERBY-1280) Derby throws ERROR XSDG1: Page could not be written to disk, please check if disk is full when there is 20+ gigs of free space

Derby throws ERROR XSDG1: Page could not be written to disk, please check if disk is full when there is 20+ gigs of free space Key: DERBY-1280 URL:

[jira] Updated: (DERBY-1219) jdbcapi/checkDataSource.java and jdbcapi/checkDataSource30.java hang intermittently with client

[ http://issues.apache.org/jira/browse/DERBY-1219?page=all ] Deepa Remesh updated DERBY-1219: Attachment: client_stack_trace_050306.txt server_stack_trace_050306.txt I talked to Kathey about this issue on IRC and she suggested trying

[jira] Commented: (DERBY-514) Integrate upgrade tests into test suite

[ http://issues.apache.org/jira/browse/DERBY-514?page=comments#action_12377621 ] Daniel John Debrunner commented on DERBY-514: - Deepa wrote: * Upgrade test runs only with jar files in classpath. It fails when run with classes folder in the

[jira] Commented: (DERBY-1261) Two triggers on same table cause ERROR 54038: Maximum depth of nested triggers was exceeded.

[ http://issues.apache.org/jira/browse/DERBY-1261?page=comments#action_12377637 ] Daniel John Debrunner commented on DERBY-1261: -- Trigger recursion occurs when there is a cycle in the firing of triggers that leads to recursion. (is that a

Re: [WWD] Review of Final Chapters (5 and 6)

I like the name - add mine to the votes for WorkingWithDerby. \Jean T. Anderson wrote: SNIP == What about naming the Wiki page WorkingWithDerby? -jean

Re: [WWD] Review of Final Chapters (5 and 6)

Stanley Bradbury wrote: I like the name - add mine to the votes for WorkingWithDerby. \Jean T. Anderson wrote: SNIP == What about naming the Wiki page WorkingWithDerby? -jean If I don't hear any objections (or better ideas) by tomorrow I'll go ahead and change the

[jira] Commented: (DERBY-1078) Be able to build Derby when JAVA_HOME is set 1.6

[ http://issues.apache.org/jira/browse/DERBY-1078?page=comments#action_12377645 ] Andrew McIntyre commented on DERBY-1078: Committed patch3 with revision 399450. Be able to build Derby when JAVA_HOME is set 1.6

[jira] Updated: (DERBY-1253) Verify that we don't raise SQLFeatureNotSupportedException for mandatory methods

[ http://issues.apache.org/jira/browse/DERBY-1253?page=all ] Rick Hillegas updated DERBY-1253: - Attachment: bug1253_verifier3_complianceChapter.diff Commmitted bug1253_verifier3_complianceChapter.diff at subversion revision 399482. This modifies the

[jira] Updated: (DERBY-1280) Derby throws ERROR XSDG1: Page could not be written to disk, please check if disk is full when there is 20+ gigs of free space

[ http://issues.apache.org/jira/browse/DERBY-1280?page=all ] Mike Matrigali updated DERBY-1280: -- Could you include in your report the following pieces of info: 1) do you by hand set page size on this table (this is not the usual case but have to ask)? 2)

[jira] Created: (DERBY-1281) JDBC4 Compliance

JDBC4 Compliance Key: DERBY-1281 URL: http://issues.apache.org/jira/browse/DERBY-1281 Project: Derby Type: Improvement Components: JDBC Versions: 10.2.0.0 Reporter: Rick Hillegas Fix For: 10.2.0.0 Here is my analysis of where

[jira] Created: (DERBY-1282) Finish client info api for JDBC4. Compliance task.

Finish client info api for JDBC4. Compliance task. -- Key: DERBY-1282 URL: http://issues.apache.org/jira/browse/DERBY-1282 Project: Derby Type: Improvement Components: JDBC Versions: 10.2.0.0 Reporter:

[jira] Created: (DERBY-1283) Fill in a deprecated but mandatory JDBC3 method: PreparedStatement.setUnicodeStream()

Fill in a deprecated but mandatory JDBC3 method: PreparedStatement.setUnicodeStream() - Key: DERBY-1283 URL: http://issues.apache.org/jira/browse/DERBY-1283 Project: Derby Type:

[jira] Created: (DERBY-1284) Fill in streaming ResultSet methods required for JDBC3 compliance

Fill in streaming ResultSet methods required for JDBC3 compliance - Key: DERBY-1284 URL: http://issues.apache.org/jira/browse/DERBY-1284 Project: Derby Type: Improvement Components: JDBC

[jira] Updated: (DERBY-1284) Fill in streaming ResultSet methods required for JDBC3 compliance

[ http://issues.apache.org/jira/browse/DERBY-1284?page=all ] Rick Hillegas updated DERBY-1284: - Component: JDBC Fix Version: 10.2.0.0 Version: 10.2.0.0 Fill in streaming ResultSet methods required for JDBC3 compliance

[jira] Commented: (DERBY-1278) hang on shutdown after getting both DriverManager and DataSource connections with security mechanism on zOS and ibm15 and networkserver client

[ http://issues.apache.org/jira/browse/DERBY-1278?page=comments#action_12377661 ] Myrna van Lunteren commented on DERBY-1278: --- Some further checking shows that this may be somewhat intermittent with 10.1... I got the following: ibm14

[jira] Created: (DERBY-1285) Finish JDBC3 Blob implementation

Finish JDBC3 Blob implementation Key: DERBY-1285 URL: http://issues.apache.org/jira/browse/DERBY-1285 Project: Derby Type: Improvement Components: JDBC Versions: 10.2.0.0 Reporter: Rick Hillegas Fix For:

[jira] Created: (DERBY-1286) Fill in Clob methods required for JDBC3 compliance

Fill in Clob methods required for JDBC3 compliance -- Key: DERBY-1286 URL: http://issues.apache.org/jira/browse/DERBY-1286 Project: Derby Type: Improvement Components: JDBC Versions: 10.2.0.0 Reporter:

[jira] Commented: (DERBY-1283) Fill in a deprecated but mandatory JDBC3 method: PreparedStatement.setUnicodeStream()

[ http://issues.apache.org/jira/browse/DERBY-1283?page=comments#action_12377662 ] Daniel John Debrunner commented on DERBY-1283: -- Seems strange to implement a deprecated api. Section 6.7 says Deprecation refers to a class, interface,

Request for comments on deciding between implementing embedded or client-server - (was: [WWD] Review of Final Chapters (5 and 6))

Starting spin-off thread on derby-user and inviting derby-dev readers to participate - see the attached thread for the current state of the discussion. DERBY-DEV readers: please help centralize this discussion by replying and monitoring this topic on DERBY-USER. OVERVIEW: The ability to

[jira] Commented: (DERBY-1283) Fill in a deprecated but mandatory JDBC3 method: PreparedStatement.setUnicodeStream()

[ http://issues.apache.org/jira/browse/DERBY-1283?page=comments#action_12377663 ] Daniel John Debrunner commented on DERBY-1283: -- Also, which section of JDBC 3.0 spec indicates that Derby is not currently in compliance with JDBC 3.0 with

[jira] Commented: (DERBY-1285) Finish JDBC3 Blob implementation

[ http://issues.apache.org/jira/browse/DERBY-1285?page=comments#action_12377664 ] Daniel John Debrunner commented on DERBY-1285: -- Which section of JDBC 3.0 spec indicates these methods are required for compilance? I see no reference to

[jira] Updated: (DERBY-1055) Security.AccessControlException in client under SecurityManager when trying to connect using EUSRIDPWD security mechanism

[ http://issues.apache.org/jira/browse/DERBY-1055?page=all ] Mike Matrigali updated DERBY-1055: -- I committed the posted patch to the 10.1 branch. m101_142:148svn commit Sendingjava\client\org\apache\derby\client\am\EncryptionManager.java Adding

hey man

Satheesh, What are you upto these days? I don't see you post as often on the derby-dev mailing list. Do you want to hook up for lunch sometime? It would be nice to hook up. cheers, Manish __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best

Re: hey man

sorry for the spam. I was trying to send this email to Satheesh :( Manish --- Manish Khettry [EMAIL PROTECTED] wrote: Satheesh, What are you upto these days? I don't see you post as often on the derby-dev mailing list. Do you want to hook up for lunch sometime? It would be nice to hook

[jira] Commented: (DERBY-1284) Fill in streaming ResultSet methods required for JDBC3 compliance

[ http://issues.apache.org/jira/browse/DERBY-1284?page=comments#action_12377667 ] Daniel John Debrunner commented on DERBY-1284: -- Same comments as DERBY-1283 - where does it say in JDBC 3 that these deprecated methods are required for

Re: hey man

Hi Manish,Things have been little hectic last few weeks. I should be back to normal soon.Sure... Lunch sounds good. I work 2-3 days from home, so we could try for lunch in Palo Alto or around there. If you are also meeting others, like Chenfang, we could do it on Monday or Wednesday, when I am in

[jira] Commented: (DERBY-1219) jdbcapi/checkDataSource.java and jdbcapi/checkDataSource30.java hang intermittently with client

[ http://issues.apache.org/jira/browse/DERBY-1219?page=comments#action_12377671 ] Bryan Pendleton commented on DERBY-1219: Hi Deepa, Can you get the DRDA trace files for the hang? I.e., set traceDirectory on the client and derby.drda.traceAll on

Derby Database Change Capturing Using Log

Hi, I am tring to build an application that captures changes in Derby database.For example, as a new query inserts data to some table comes, I want to be able to get that change without using trigger for scalability and loose coupling reasons. The solution I'm considering is to use Derby's

Re: Derby Database Change Capturing Using Log

I am tring to build an application that captures changes in Derby database.For example, as a new query inserts data to some table comes, I want to be able to get that change without using trigger for scalability and loose coupling reasons. What about using something like P6Spy

Re: [jira] Commented: (DERBY-1283) Fill in a deprecated but mandatory JDBC3 method: PreparedStatement.setUnicodeStream()

Very simple, just because it is deprecated, it does not mean it can be ignored.  Bottom line, it is required to be there. There are no plans to remove these methods from JDBC. Daniel John Debrunner (JIRA) wrote: [

Re: [jira] Commented: (DERBY-1283) Fill in a deprecated but mandatory JDBC3 method: PreparedStatement.setUnicodeStream()

The compliance chapter has seen significant clarifications for JDBC 4 to clarify what is and is not required.  If you implement and interface for a data type such as blob/clob all methods must be implemented otherwise you do not support the data type. Daniel John Debrunner (JIRA) wrote:

Re: [jira] Commented: (DERBY-1283) Fill in a deprecated but mandatory JDBC3 method: PreparedStatement.setUnicodeStream()

Lance J. Andersen wrote: Very simple, just because it is deprecated, it does not mean it can be ignored. Bottom line, it is required to be there. According to which section of JDBC 3.0? Dan.

Re: [jira] Commented: (DERBY-1283) Fill in a deprecated but mandatory JDBC3 method: PreparedStatement.setUnicodeStream()

Lance J. Andersen wrote: The compliance chapter has seen significant clarifications for JDBC 4 to clarify what is and is not required. If you implement and interface for a data type such as blob/clob all methods must be implemented otherwise you do not support the data type. So this is a

Re: [jira] Commented: (DERBY-1283) Fill in a deprecated but mandatory JDBC3 method: PreparedStatement.setUnicodeStream()

Lance J. Andersen wrote: The compliance chapter has seen significant clarifications for JDBC 4 to clarify what is and is not required. If you implement and interface for a data type such as blob/clob all methods must be implemented otherwise you do not support the data type. Is this a recent