[jira] Updated: (DERBY-623) Derby monitor accesses two system properties without using a privileged block when built sane=true

[ http://issues.apache.org/jira/browse/DERBY-623?page=all ] Kristian Waagan updated DERBY-623: -- Attachment: (was: DERBY-623-2a-javadoc.diff) Derby monitor accesses two system properties without using a privileged block when built sane=true

[jira] Updated: (DERBY-623) Derby monitor accesses two system properties without using a privileged block when built sane=true

[ http://issues.apache.org/jira/browse/DERBY-623?page=all ] Kristian Waagan updated DERBY-623: -- Attachment: (was: DERBY-623-2a-javadoc.stat) Derby monitor accesses two system properties without using a privileged block when built sane=true

[jira] Updated: (DERBY-623) Derby monitor accesses two system properties without using a privileged block when built sane=true

[ http://issues.apache.org/jira/browse/DERBY-623?page=all ] Kristian Waagan updated DERBY-623: -- Attachment: DERBY-623-1a.diff DERBY-623-1a.stat 'DERBY-623-1a.diff' is a patch changing BaseMonitor to use privileged blocks for reading

[jira] Updated: (DERBY-623) Derby monitor accesses two system properties without using a privileged block when built sane=true

[ http://issues.apache.org/jira/browse/DERBY-623?page=all ] Kristian Waagan updated DERBY-623: -- Other Info: [Patch available] Patch ready for review :) Derby monitor accesses two system properties without using a privileged block when built sane

[jira] Created: (DERBY-1088) Verify handling of invalid encryption keys

Verify handling of invalid encryption keys --- Key: DERBY-1088 URL: http://issues.apache.org/jira/browse/DERBY-1088 Project: Derby Type: Task Components: Services Versions: 10.2.0.0 Reporter: Kristian Waagan

[jira] Closed: (DERBY-788) 'store/encryptionKey.sql' fails on Solaris 10

[ http://issues.apache.org/jira/browse/DERBY-788?page=all ] Kristian Waagan closed DERBY-788: - Fix verified. Created DERBY-1088 to track general issues/weaknesses in the way external encryption keys are handled. 'store/encryptionKey.sql' fails

[jira] Commented: (DERBY-623) Derby monitor accesses two system properties without using a privileged block when built sane=true

[ http://issues.apache.org/jira/browse/DERBY-623?page=comments#action_12369559 ] Kristian Waagan commented on DERBY-623: --- By looking at the description of the bug, I really can't see that the changes I implemented are outside the scope of the bug

[jira] Updated: (DERBY-623) Derby monitor accesses two system properties without using a privileged block when built sane=true

[ http://issues.apache.org/jira/browse/DERBY-623?page=all ] Kristian Waagan updated DERBY-623: -- Attachment: DERBY-623-1b.diff DERBY-623-1b.stat Dan, I see your point now! I do still mean we need another Jira though, to track cleaning

[jira] Updated: (DERBY-1061) SqlException while fetching message results in recursive calls between SqlException.getSQLException and Sqlca.getJDBCMessage

[ http://issues.apache.org/jira/browse/DERBY-1061?page=all ] Kristian Waagan updated DERBY-1061: --- Attachment: JDBC4StackOverflowErrorReproduction.java derby-1061_2-unix.diff Had some problems applying diff on Linux, seems to be related

[jira] Created: (DERBY-1095) Closing an embedded connection does not seem to close associated EmbedStatements

Components: JDBC Versions: 10.2.0.0 Reporter: Kristian Waagan Priority: Minor Closing an embedded connection (calling EmbedConnection.close()) does not seem to close associated EmbedStatements. The severity of the bug is not determined. The least severe case is that the internal

[jira] Updated: (DERBY-1095) Closing an embedded connection does not seem to close associated EmbedStatements

[ http://issues.apache.org/jira/browse/DERBY-1095?page=all ] Kristian Waagan updated DERBY-1095: --- Attachment: Derby1095Repro.java Simple repro for demonstrating the issue. Compile and run with JDK 1.6. Derby must also be built with JDK 1.6. The repro

[jira] Updated: (DERBY-953) Add miscellaneous Statement methods introduced by JDBC 4

[ http://issues.apache.org/jira/browse/DERBY-953?page=all ] Kristian Waagan updated DERBY-953: -- Attachment: DERBY-953-1a.diff DERBY-953-1a.stat Uploaded patch 'DERBY-953-1a.diff' for implementing Statement.isClosed() on both client

[jira] Deleted: (DERBY-1096) Add JUnit tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1096?page=all ] Kristian Waagan deleted DERBY-1096: --- Add JUnit tests for Statement.isClosed() Key: DERBY-1096 URL: http://issues.apache.org

[jira] Created: (DERBY-1097) Add tests for Statement.isClosed()

: Kristian Waagan Assigned to: Kristian Waagan Add tests for Statement.isClosed() (implemented as part of DERBY-953). The tests are already written, but because of some confusion and diverging paths regarding how to get connections when running JUnit tests, they are held back. -- This message

[jira] Commented: (DERBY-1061) SqlException while fetching message results in recursive calls between SqlException.getSQLException and Sqlca.getJDBCMessage

[ http://issues.apache.org/jira/browse/DERBY-1061?page=comments#action_12370067 ] Kristian Waagan commented on DERBY-1061: I tried the repro script with unpatched trunk, 'derby-1061_v2' diff and 'derby-1061-david.diff'. For me, running on Gentoo

[jira] Commented: (DERBY-1095) Closing an embedded connection does not seem to close associated EmbedStatements

[ http://issues.apache.org/jira/browse/DERBY-1095?page=comments#action_12370077 ] Kristian Waagan commented on DERBY-1095: I see your point, but I still think Derby is buggy. The repro script executes a statement, closes the connection then asks

[jira] Updated: (DERBY-919) improve pattern for setting up junit tests

[ http://issues.apache.org/jira/browse/DERBY-919?page=all ] Kristian Waagan updated DERBY-919: -- Attachment: BasicDerbyJUnitTest.java BasicDerbyJUnitTestTest.java BasicDerbyJUnitTest.html In my opinion DerbyJUnitTest does

[jira] Updated: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=all ] Kristian Waagan updated DERBY-1097: --- Attachment: StatementTest.java StatementTestSetup.java Updated preliminary tests for Statement.isClosed(). Feedback is appreciated

[jira] Commented: (DERBY-1095) Closing an embedded connection does not seem to close associated EmbedStatements

[ http://issues.apache.org/jira/browse/DERBY-1095?page=comments#action_12370138 ] Kristian Waagan commented on DERBY-1095: No Jiras have been opened. First patch for Statement.isClosed() is not even committed yet (DERBY-953). Code

[jira] Commented: (DERBY-919) improve pattern for setting up junit tests

[ http://issues.apache.org/jira/browse/DERBY-919?page=comments#action_12370182 ] Kristian Waagan commented on DERBY-919: --- I agree that the naming of the class can be changed. I am not so sure if I fully agree with the proposed change regarding setUp

[jira] Resolved: (DERBY-809) Incorrect documentation for 'NetworkServerControl.logConnections(boolean)'

[ http://issues.apache.org/jira/browse/DERBY-809?page=all ] Kristian Waagan resolved DERBY-809: --- Fix Version: (was: 10.1.3.0) Resolution: Fixed Documentation has been fixed. I will close this issue in a few days, unless someone signals

[jira] Commented: (DERBY-1095) Closing an embedded connection does not seem to close associated EmbedStatements

[ http://issues.apache.org/jira/browse/DERBY-1095?page=comments#action_12370338 ] Kristian Waagan commented on DERBY-1095: I do not disagree that it is easy to implement isClosed to return the intended results (I commented this when uploading

[jira] Commented: (DERBY-1095) Closing an embedded connection does not seem to close associated EmbedStatements

[ http://issues.apache.org/jira/browse/DERBY-1095?page=comments#action_12370518 ] Kristian Waagan commented on DERBY-1095: Thanks Dan. The slides are nice :) Assuming they are still up-to-date, I would recommend people who haven't looked at them

[jira] Commented: (DERBY-919) improve pattern for setting up junit tests

[ http://issues.apache.org/jira/browse/DERBY-919?page=comments#action_12370620 ] Kristian Waagan commented on DERBY-919: --- Do we still need to have clients for both DB2 JCC and the old net framework? Based on contents of various classes, there seem

[jira] Assigned: (DERBY-919) improve pattern for setting up junit tests

[ http://issues.apache.org/jira/browse/DERBY-919?page=all ] Kristian Waagan reassigned DERBY-919: - Assign To: Kristian Waagan improve pattern for setting up junit tests -- Key: DERBY-919

[jira] Updated: (DERBY-919) improve pattern for setting up junit tests

[ http://issues.apache.org/jira/browse/DERBY-919?page=all ] Kristian Waagan updated DERBY-919: -- Attachment: BaseJUnitTestClasses-v1.tar Another go at establishing base classes for JUnit tests - 'BaseJUnitTestClasses-v1.tar' (tar contains 4 files

[jira] Updated: (DERBY-953) Add miscellaneous Statement methods introduced by JDBC 4

[ http://issues.apache.org/jira/browse/DERBY-953?page=all ] Kristian Waagan updated DERBY-953: -- Attachment: DERBY-953-2a.diff 'DERBY-953-2a.diff' implements EmbedStatement.isClosed() in different way. If the statement is marked as active, it goes

[jira] Updated: (DERBY-953) Add miscellaneous Statement methods introduced by JDBC 4

[ http://issues.apache.org/jira/browse/DERBY-953?page=all ] Kristian Waagan updated DERBY-953: -- Other Info: [Patch available] Add miscellaneous Statement methods introduced by JDBC 4

[jira] Updated: (DERBY-919) improve pattern for setting up junit tests

[ http://issues.apache.org/jira/browse/DERBY-919?page=all ] Kristian Waagan updated DERBY-919: -- Attachment: BaseJUnitTestClasses-v2.tar Thank you Andreas. See answers for your comments below. 1. I don't think this is necessary. An exception

[jira] Closed: (DERBY-623) Derby monitor accesses two system properties without using a privileged block when built sane=true

[ http://issues.apache.org/jira/browse/DERBY-623?page=all ] Kristian Waagan closed DERBY-623: - Fix Version: 10.2.0.0 Resolution: Fixed Closing the issue. No problems reported regarding the fix. Derby monitor accesses two system properties

[jira] Created: (DERBY-1122) Improve base JUnit testing classes

Improve base JUnit testing classes -- Key: DERBY-1122 URL: http://issues.apache.org/jira/browse/DERBY-1122 Project: Derby Type: Task Components: Test Versions: 10.3.0.0, 10.2.0.0 Reporter: Kristian Waagan Priority

[jira] Updated: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=all ] Kristian Waagan updated DERBY-1097: --- Attachment: StatementTest.java-v1 StatementTestSetup.java-v1 Updated tests to run with the new base JUnit test classes. Had to rename

[jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12371051 ] Kristian Waagan commented on DERBY-1097: Answering Rick's comments of 17th of March. 1) As is already stated, this test can be run from any suite by simply adding

[jira] Updated: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=all ] Kristian Waagan updated DERBY-1097: --- Attachment: DERBY-1097-2a.stat DERBY-1097-2a.diff Answering David's comments of 18th of March, and uploading 'DERBY-1097-2a.diff' (patch

[jira] Assigned: (DERBY-944) Code ROWID methods for JDBC4 support

[ http://issues.apache.org/jira/browse/DERBY-944?page=all ] Kristian Waagan reassigned DERBY-944: - Assign To: Kristian Waagan Code ROWID methods for JDBC4 support Key: DERBY-944 URL: http

[jira] Updated: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=all ] Kristian Waagan updated DERBY-1097: --- Attachment: DERBY-1097-2b.diff Updated patch, 'DERBY-1097-2b.diff'. See 'DERBY-1097-2a.stat' svn status. Previous patch was not the correct patch

[jira] Commented: (DERBY-1133) Split jdbc4 tests so that the suite can be run independently under the embedded and DerbyNetClients like other Derby test suites

[ http://issues.apache.org/jira/browse/DERBY-1133?page=comments#action_12371295 ] Kristian Waagan commented on DERBY-1133: It is a bit unclear to me why we need to have two different suites. Is it done to make it easier to keep the overview

[jira] Commented: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=comments#action_12371394 ] Kristian Waagan commented on DERBY-1097: I tried it in my environment, and it worked by simply adding the line jdbc4/StatementTest.junit to the jdbc40.runall file

[jira] Updated: (DERBY-953) Add miscellaneous Statement methods introduced by JDBC 4

[ http://issues.apache.org/jira/browse/DERBY-953?page=all ] Kristian Waagan updated DERBY-953: -- Attachment: DERBY-953-3a.diff 'DERBY-953-3a.diff' is a patch implementing pretty much what David suggested. I made some corrections, and I also had to add

[jira] Created: (DERBY-1149) 'jdbc40/StatementTest.junit' fails under DerbyNetClient

: 10.2.0.0 Environment: JDK 1.6 (b76 used, believed to apply to all) Reporter: Kristian Waagan Assigned to: Kristian Waagan One of the tests in jdbc40/StatementTest.junit fails with the following message: Attempt to shutdown framework: DerbyNetClient 0 add F. There was 1 failure

[jira] Commented: (DERBY-1149) 'jdbc40/StatementTest.junit' fails under DerbyNetClient

[ http://issues.apache.org/jira/browse/DERBY-1149?page=comments#action_12371720 ] Kristian Waagan commented on DERBY-1149: I will look into this, and fix the test by either adjusting the expected exception message, or compare SQLStates if it has

[jira] Commented: (DERBY-1149) 'jdbc40/StatementTest.junit' fails under DerbyNetClient

[ http://issues.apache.org/jira/browse/DERBY-1149?page=comments#action_12371754 ] Kristian Waagan commented on DERBY-1149: I need a little help on my issue. The following diff is from r388309: --- /db/derby/code/trunk/java/client/org/apache/derby

[jira] Closed: (DERBY-1097) Add tests for Statement.isClosed()

[ http://issues.apache.org/jira/browse/DERBY-1097?page=all ] Kristian Waagan closed DERBY-1097: -- Closed, tests added and run under jdbc40 suite. Add tests for Statement.isClosed() -- Key: DERBY-1097

[jira] Closed: (DERBY-953) Add miscellaneous Statement methods introduced by JDBC 4

[ http://issues.apache.org/jira/browse/DERBY-953?page=all ] Kristian Waagan closed DERBY-953: - Task completed. Add miscellaneous Statement methods introduced by JDBC 4 Key: DERBY

[jira] Updated: (DERBY-944) Code ROWID methods for JDBC4 support

[ http://issues.apache.org/jira/browse/DERBY-944?page=all ] Kristian Waagan updated DERBY-944: -- Attachment: DERBY-944.stat DERBY-944-javadoc.diff DERBY-944-tests.diff Submitted tests for checking that methods related

[jira] Created: (DERBY-1162) Add mechanism to assert/compare SQLStates

environment Reporter: Kristian Waagan Assigned to: Kristian Waagan Priority: Minor The JUnit test environment needs a mechanism to assert/compare SQLStates. The goal is to be able to reference states from SQLState without having to care if the length of the identifier is 5,7 or more characters

[jira] Updated: (DERBY-1162) Add mechanism to assert/compare SQLStates

[ http://issues.apache.org/jira/browse/DERBY-1162?page=all ] Kristian Waagan updated DERBY-1162: --- Attachment: DERBY-1162-1a.diff 'DERBY-1162-1a.diff' adds method 'assertSQLState' to BaseJDBCTestCase. Please review/commit. Add mechanism to assert

[jira] Commented: (DERBY-1149) 'jdbc40/StatementTest.junit' fails under DerbyNetClient

[ http://issues.apache.org/jira/browse/DERBY-1149?page=comments#action_12372240 ] Kristian Waagan commented on DERBY-1149: This patch will (and does) fail, due to the way SQLStates are compared. I will brush up the patch, only changing things

[jira] Updated: (DERBY-1149) 'jdbc40/StatementTest.junit' fails under DerbyNetClient

[ http://issues.apache.org/jira/browse/DERBY-1149?page=all ] Kristian Waagan updated DERBY-1149: --- Attachment: DERBY-1149-2a-StatementTestFailure.diff Uploaded 'DERBY-1149-2a-StatementTestFailure.diff' with two changes in StatementTest.java only. Now

[jira] Closed: (DERBY-1162) Add mechanism to assert/compare SQLStates

[ http://issues.apache.org/jira/browse/DERBY-1162?page=all ] Kristian Waagan closed DERBY-1162: -- Change verified. Add mechanism to assert/compare SQLStates - Key: DERBY-1162 URL: http

[jira] Assigned: (DERBY-1147) Implement miscellaneous CallableStatement methods added by JDBC4

[ http://issues.apache.org/jira/browse/DERBY-1147?page=all ] Kristian Waagan reassigned DERBY-1147: -- Assign To: Kristian Waagan Implement miscellaneous CallableStatement methods added by JDBC4

[jira] Updated: (DERBY-1149) 'jdbc40/StatementTest.junit' fails under DerbyNetClient

[ http://issues.apache.org/jira/browse/DERBY-1149?page=all ] Kristian Waagan updated DERBY-1149: --- Attachment: DERBY-1149-3a-StatementTestFailure.diff 'DERBY-1149-3a-StatementTestFailure.diff' changes the identifier 25000.S.1 to 25001, and removes

[jira] Commented: (DERBY-1149) 'jdbc40/StatementTest.junit' fails under DerbyNetClient

[ http://issues.apache.org/jira/browse/DERBY-1149?page=comments#action_12372394 ] Kristian Waagan commented on DERBY-1149: The following part of the patch does not make sense to me: +if ( ! expectedState.equals(sqle.getSQLState

[jira] Updated: (DERBY-1147) Implement miscellaneous CallableStatement methods added by JDBC4

[ http://issues.apache.org/jira/browse/DERBY-1147?page=all ] Kristian Waagan updated DERBY-1147: --- Attachment: derby-1147-1a-missing-methods.diff derby-1147-1a-missing-methods.stat 'derby-1147-1a-missing-methods.diff' adds the missing

[jira] Commented: (DERBY-940) Add JDBC 4 Wrapper support

[ http://issues.apache.org/jira/browse/DERBY-940?page=comments#action_12372694 ] Kristian Waagan commented on DERBY-940: --- I only had a look at the test code for CallableStatementTest.java. I have the following comments (also see the separate comment

[jira] Created: (DERBY-1184) 'CallableStatement.registerOutParameter(int,int,String)' does nothing in client driver

: Bug Components: JDBC Versions: 10.2.0.0 Environment: Derby network client Reporter: Kristian Waagan Priority: Minor The method 'CallableStatement.registerOutParameter(int,int,String)' does nothing in the client driver. As stated in DERBY-447, the method throws

[jira] Assigned: (DERBY-1184) 'CallableStatement.registerOutParameter(int,int,String)' does nothing in client driver

[ http://issues.apache.org/jira/browse/DERBY-1184?page=all ] Kristian Waagan reassigned DERBY-1184: -- Assign To: Kristian Waagan 'CallableStatement.registerOutParameter(int,int,String)' does nothing in client driver

[jira] Updated: (DERBY-1184) 'CallableStatement.registerOutParameter(int,int,String)' does nothing in client driver

[ http://issues.apache.org/jira/browse/DERBY-1184?page=all ] Kristian Waagan updated DERBY-1184: --- Attachment: derby-1184-1a.diff derby-1184-1a.stat 'derby-1184-1a.diff' changes the method CallableStatement.registerOutParameter(int,int

[jira] Updated: (DERBY-1184) 'CallableStatement.registerOutParameter(int,int,String)' does nothing in client driver

[ http://issues.apache.org/jira/browse/DERBY-1184?page=all ] Kristian Waagan updated DERBY-1184: --- Derby Info: [Patch Available] 'CallableStatement.registerOutParameter(int,int,String)' does nothing in client driver

[jira] Commented: (DERBY-477) JDBC client and embedded drivers differ wrt API subset supported

[ http://issues.apache.org/jira/browse/DERBY-477?page=comments#action_12373436 ] Kristian Waagan commented on DERBY-477: --- CallableStatement.registerOutParameter(int paramIndex, int sqlType, String typeName) is addressed by DERBY-1184. When some more

[jira] Commented: (DERBY-1184) 'CallableStatement.registerOutParameter(int,int,String)' does nothing in client driver

[ http://issues.apache.org/jira/browse/DERBY-1184?page=comments#action_12373442 ] Kristian Waagan commented on DERBY-1184: Yes, a test should be added, but since the existing test was canon based test, I did not find the time to add a test

[jira] Assigned: (DERBY-1184) 'CallableStatement.registerOutParameter(int,int,String)' does nothing in client driver

[ http://issues.apache.org/jira/browse/DERBY-1184?page=all ] Kristian Waagan reassigned DERBY-1184: -- Assign To: (was: Kristian Waagan) I won't be working more on this for a long time... A test is missing, please add

[jira] Updated: (DERBY-1147) Implement miscellaneous CallableStatement methods added by JDBC4

[ http://issues.apache.org/jira/browse/DERBY-1147?page=all ] Kristian Waagan updated DERBY-1147: --- Attachment: derby-1147-2a-getcharacterstream.stat derby-1147-2a-getcharacterstream.diff 'derby-1147-2a-getcharacterstream.diff

[jira] Commented: (DERBY-1184) 'CallableStatement.registerOutParameter(int,int,String)' does nothing in client driver

[ http://issues.apache.org/jira/browse/DERBY-1184?page=comments#action_12373590 ] Kristian Waagan commented on DERBY-1184: derbyall run without failures (Solaris10, Java 1.5, 646 tests run). 'CallableStatement.registerOutParameter(int,int,String

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

[ http://issues.apache.org/jira/browse/DERBY-1181?page=comments#action_12373593 ] Kristian Waagan commented on DERBY-1181: Because Derby does not support named parameters, the list of methods below will not be implemented at this time. It has been

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

[ http://issues.apache.org/jira/browse/DERBY-1180?page=all ] Kristian Waagan reassigned DERBY-1180: -- Assign To: Kristian Waagan Add vacuous implementations of missing JDBC4 methods

[jira] Commented: (DERBY-1184) 'CallableStatement.registerOutParameter(int,int,String)' does nothing in client driver

[ http://issues.apache.org/jira/browse/DERBY-1184?page=comments#action_12373649 ] Kristian Waagan commented on DERBY-1184: Code changes are okay and works as expected, but the test has become out of synch with the SQL states. In revision 392060

[jira] Closed: (DERBY-1184) 'CallableStatement.registerOutParameter(int,int,String)' does nothing in client driver

[ http://issues.apache.org/jira/browse/DERBY-1184?page=all ] Kristian Waagan closed DERBY-1184: -- Confirmed that the test passes (DerbyNetClient only). Thanks for writing the test and fixing the problem Bryan! 'CallableStatement.registerOutParameter

[jira] Updated: (DERBY-1147) Implement miscellaneous CallableStatement methods added by JDBC4

[ http://issues.apache.org/jira/browse/DERBY-1147?page=all ] Kristian Waagan updated DERBY-1147: --- Attachment: derby-1147-2b-getcharacterstream.stat derby-1147-2b-getcharacterstream.diff 'derby-1147-2b-getcharacterstream.diff

[jira] Updated: (DERBY-1147) Implement miscellaneous CallableStatement methods added by JDBC4

[ http://issues.apache.org/jira/browse/DERBY-1147?page=all ] Kristian Waagan updated DERBY-1147: --- Derby Info: [Patch Available] Implement miscellaneous CallableStatement methods added by JDBC4

[jira] Updated: (DERBY-1198) jdbc/StatementTest.java uses SQLState directly

[ http://issues.apache.org/jira/browse/DERBY-1198?page=all ] Kristian Waagan updated DERBY-1198: --- Attachment: derby-1198-rmimport.diff 'derby-1198-rmimport.diff' removes an unused import in StatementTest. After the new SQLStateConstants

[jira] Closed: (DERBY-1198) jdbc/StatementTest.java uses SQLState directly

[ http://issues.apache.org/jira/browse/DERBY-1198?page=all ] Kristian Waagan closed DERBY-1198: -- Ran the jdbc40 suite again to confirm the fix didn't break anything. Run passed. jdbc/StatementTest.java uses SQLState directly

[jira] Created: (DERBY-1242) Write test(s) for ParameterMetaData and the getParameterMetaData-methods in JDBC4

Components: JDBC, Test Versions: 10.2.0.0 Reporter: Kristian Waagan There are no tests for ParameterMetaData in JDBC4. Several new methods returning ParameterMetaData objects have recently been added, and these methods and their results should be checked by tests. -- This message

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

[ http://issues.apache.org/jira/browse/DERBY-1180?page=all ] Kristian Waagan updated DERBY-1180: --- Attachment: derby-1180-1a-embedded.diff derby-1180-1a-embedded.stat 'derby-1180-1a-embedded.diff' addresses missing JDBC4 signatures

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

[ http://issues.apache.org/jira/browse/DERBY-1180?page=all ] Kristian Waagan updated DERBY-1180: --- Derby Info: [Patch Available] Partial patch 'derby-1180-1a-embedded.diff' available. Add vacuous implementations of missing JDBC4 methods

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

[ http://issues.apache.org/jira/browse/DERBY-1180?page=comments#action_12375558 ] Kristian Waagan commented on DERBY-1180: All the comments are valid, but since I am only adding placeholders that throw not implemented exceptions, I decided

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

[ http://issues.apache.org/jira/browse/DERBY-1180?page=all ] Kristian Waagan updated DERBY-1180: --- Attachment: derby-1180-2a-client.diff derby-1180-2a-client.stat 'derby-1180-2a-client.diff' adds 10 more missing signatures

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

[ http://issues.apache.org/jira/browse/DERBY-1180?page=all ] Kristian Waagan updated DERBY-1180: --- Attachment: derby-1180-3a-testing.diff derby-1180-3a-testing.stat 'derby-1180-3a-testing.diff' implements tests for the missing

[jira] Closed: (DERBY-1147) Implement miscellaneous CallableStatement methods added by JDBC4

[ http://issues.apache.org/jira/browse/DERBY-1147?page=all ] Kristian Waagan closed DERBY-1147: -- Resolution: Fixed Patch committed and no problems reported. Closing issue. Implement miscellaneous CallableStatement methods added by JDBC4

[jira] Commented: (DERBY-1235) Move isPoolable() and setPoolable() from PreparedStatement to Statement

[ http://issues.apache.org/jira/browse/DERBY-1235?page=comments#action_12376427 ] Kristian Waagan commented on DERBY-1235: Hi Dyre. Thanks for the patch. I had a look at it, and have the following comments: 1) The JavaDoc states isPoolable should

[jira] Updated: (DERBY-1235) Move isPoolable() and setPoolable() from PreparedStatement to Statement

[ http://issues.apache.org/jira/browse/DERBY-1235?page=all ] Kristian Waagan updated DERBY-1235: --- Derby Info: [Patch Available] My comments have all beed addressed, and I think the patch (' derby-1235.v2.diff') looks solid and is ready for commit. I

[jira] Created: (DERBY-1254) XAConnection uses NetConnection as underlying physical connection for JDBC4/Java 1.6

Components: JDBC Versions: 10.2.0.0 Environment: DerbyNetClient Reporter: Kristian Waagan When running under DerbyNetClient (using Derby network server) using Java 1.6, XAConnection.getConnection() returns a NetConnection instance instead of NetConnection40 instance

[jira] Closed: (DERBY-1149) 'jdbc40/StatementTest.junit' fails under DerbyNetClient

[ http://issues.apache.org/jira/browse/DERBY-1149?page=all ] Kristian Waagan closed DERBY-1149: -- Problem fixed, isse closed. 'jdbc40/StatementTest.junit' fails under DerbyNetClient

[jira] Closed: (DERBY-809) Incorrect documentation for 'NetworkServerControl.logConnections(boolean)'

[ http://issues.apache.org/jira/browse/DERBY-809?page=all ] Kristian Waagan closed DERBY-809: - Closed, no interest to port this has been detected. Incorrect documentation for 'NetworkServerControl.logConnections(boolean

[jira] Updated: (DERBY-746) NullPointerException when 'encryptionKey' length is an odd number, or it contains invalid chars

[ http://issues.apache.org/jira/browse/DERBY-746?page=all ] Kristian Waagan updated DERBY-746: -- Fix Version: 10.1.3.0 10.1.2.4 Derby Info: [Release Note Needed] Set fix version to indicate porting. NullPointerException when

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

[ http://issues.apache.org/jira/browse/DERBY-1180?page=all ] Kristian Waagan updated DERBY-1180: --- Attachment: derby-1180-4a-logcialconnection_and_tests.diff derby-1180-4a-logcialconnection_and_tests.stat 'derby-1180-4a

[jira] Assigned: (DERBY-1238) Add vacuous implementations for Connection.createStruct() and Connection.createArray()

[ http://issues.apache.org/jira/browse/DERBY-1238?page=all ] Kristian Waagan reassigned DERBY-1238: -- Assign To: Kristian Waagan (was: Olav Sandstaa) Add vacuous implementations for Connection.createStruct() and Connection.createArray

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

[ http://issues.apache.org/jira/browse/DERBY-1180?page=all ] Kristian Waagan updated DERBY-1180: --- Attachment: derby-1180-4b-logicalconnection_and_tests.diff 'derby-1180-4b-logicalconnection_and_tests.diff' fixes the problem with a renamed class

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

[ http://issues.apache.org/jira/browse/DERBY-1180?page=all ] Kristian Waagan updated DERBY-1180: --- Attachment: derby-1180-4c-logicalconnection_and_tests.diff Sorry, forgot to update the patch with your fix Rick. 'derby-1180-4c

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

[ http://issues.apache.org/jira/browse/DERBY-1180?page=comments#action_12377393 ] Kristian Waagan commented on DERBY-1180: Thanks for committing Rick. Sorry for the compile warning, I did not even see it... Could a committer please delete the file

[jira] Updated: (DERBY-1146) Verify that JDBC4 signatures satisfied

[ http://issues.apache.org/jira/browse/DERBY-1146?page=all ] Kristian Waagan updated DERBY-1146: --- Attachment: derby-1146-v2-enable.diff 'derby-1146-v2-enable.diff' enables the VerifySignatures patch, as it no longer fails. In addition, it sorts

[jira] Updated: (DERBY-1238) Add vacuous implementations for Connection.createStruct() and Connection.createArray()

[ http://issues.apache.org/jira/browse/DERBY-1238?page=all ] Kristian Waagan updated DERBY-1238: --- Attachment: derby-1238-1a.diff derby-1238-1a.stat 'derby-1238-1a.diff' add methods createArray and createStruct. They all throw

[jira] Updated: (DERBY-1238) Add vacuous implementations for Connection.createStruct() and Connection.createArray()

[ http://issues.apache.org/jira/browse/DERBY-1238?page=all ] Kristian Waagan updated DERBY-1238: --- Derby Info: [Patch Available] Add vacuous implementations for Connection.createStruct() and Connection.createArray

[jira] Updated: (DERBY-1146) Verify that JDBC4 signatures satisfied

[ http://issues.apache.org/jira/browse/DERBY-1146?page=all ] Kristian Waagan updated DERBY-1146: --- Derby Info: [Patch Available] Verify that JDBC4 signatures satisfied -- Key: DERBY-1146 URL

[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

[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] Commented: (DERBY-1234) Verify that we raise SQLException when calling methods on closed java.sql objects

[ http://issues.apache.org/jira/browse/DERBY-1234?page=comments#action_12377796 ] Kristian Waagan commented on DERBY-1234: Although not directly related to this issue, I would like to comment that some care should be taken to ensure exceptions

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

[ http://issues.apache.org/jira/browse/DERBY-1180?page=all ] Kristian Waagan closed DERBY-1180: -- No more work expected for this issue; closing it. If the JDBC 4 spec changes, it will be handled under other and more specific Jiras. Add vacuous

[jira] Closed: (DERBY-944) Code ROWID methods for JDBC4 support

[ http://issues.apache.org/jira/browse/DERBY-944?page=all ] Kristian Waagan closed DERBY-944: - Resolution: Fixed Closing issue. Code ROWID methods for JDBC4 support Key: DERBY-944 URL

[jira] Commented: (DERBY-1341) LOB setBytes method(s) are currently no supported, but part of the Java 1.4 JDBC interface

[ http://issues.apache.org/jira/browse/DERBY-1341?page=comments#action_12413381 ] Kristian Waagan commented on DERBY-1341: (I assume the 'getBytes' in the description can be replaced with 'setBytes') Derby currently only supports the two setBytes

<    4   5   6   7   8   9   10   11   12   13   >