[jira] Commented: (DERBY-3421) Remove unused code for caching of connect bytes
[ https://issues.apache.org/jira/browse/DERBY-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569529#action_12569529 ] Kristian Waagan commented on DERBY-3421: Tests ran fine with the patch applied (Solaris 10, Sun JDK 1.6). Remove unused code for caching of connect bytes --- Key: DERBY-3421 URL: https://issues.apache.org/jira/browse/DERBY-3421 Project: Derby Issue Type: Improvement Components: Network Client Affects Versions: 10.4.0.0 Reporter: Kristian Waagan Assignee: Kristian Waagan Priority: Minor Attachments: derby-3421-1a-removal.diff, derby-3421-1a-removal.stat The client driver has code for caching connect bytes, but it is not used. This unused code clutters the rest of the code and makes it harder to understand. Secondly, the variable used to determine if the cached connect bytes can be used is public in am.Connection. If someone has historic information about this feature, it would be nice if they could add the information to this Jira. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3375) Localize new error messages added in 10.3
[ https://issues.apache.org/jira/browse/DERBY-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569550#action_12569550 ] Dyre Tjeldvoll commented on DERBY-3375: --- I copied the guts of the MessageBuilder class and managed to parse and traverse the messages.xml file in a standalone program. I think I see how I can can add nodes/elements to the resulting org.w3c.dom.Document tree. But how do I write the resulting tree back to a new file? What's the best way to add the translated messages to the xml structure? Can I just add new tags? E.g. text_en, text_de_DE...? Localize new error messages added in 10.3 - Key: DERBY-3375 URL: https://issues.apache.org/jira/browse/DERBY-3375 Project: Derby Issue Type: Improvement Components: Localization Affects Versions: 10.3.2.1 Reporter: Dyre Tjeldvoll Priority: Minor Fix For: 10.4.0.0 Attachments: CheckMessages.java, checkMessages.sql, derby-3375.diff, drda_messages.zip, engine_messages.zip New error messages added in 10.3 have not been localized. Should translate these into as many languages as possible. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3349) Nested WHERE EXISTS queries need improved testing
[ https://issues.apache.org/jira/browse/DERBY-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Nielsen updated DERBY-3349: -- Derby Info: [Patch Available] Assignee: Thomas Nielsen Nested WHERE EXISTS queries need improved testing - Key: DERBY-3349 URL: https://issues.apache.org/jira/browse/DERBY-3349 Project: Derby Issue Type: Improvement Components: Test Reporter: Thomas Nielsen Assignee: Thomas Nielsen Attachments: d3349-1.diff, d3349-1.stat, d3349-2.diff, d3349-3.diff DERBY-3301 reported an error in subquery flattening of nested WHERE EXISTS clauses, or WHERE EXISTS subqueries. The query returned the wrong number of rows. There is currently some tests for WHERE EXISTS, but none for nested WHERE EXISTS clauses. See DERBY-3301 for a full sql repro. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3349) Nested WHERE EXISTS queries need improved testing
[ https://issues.apache.org/jira/browse/DERBY-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Nielsen updated DERBY-3349: -- Attachment: d3349-3.diff Attaching updated d3349-3.diff that runs the last two combinations WHERE EXISTS ... WHERE ANY WHERE ANY ... WHERE ANY The test was made part of the suite as part of DERBY-3301. The updated test passes when run against the trunk. Nested WHERE EXISTS queries need improved testing - Key: DERBY-3349 URL: https://issues.apache.org/jira/browse/DERBY-3349 Project: Derby Issue Type: Improvement Components: Test Reporter: Thomas Nielsen Attachments: d3349-1.diff, d3349-1.stat, d3349-2.diff, d3349-3.diff DERBY-3301 reported an error in subquery flattening of nested WHERE EXISTS clauses, or WHERE EXISTS subqueries. The query returned the wrong number of rows. There is currently some tests for WHERE EXISTS, but none for nested WHERE EXISTS clauses. See DERBY-3301 for a full sql repro. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3301) Incorrect result from query with nested EXIST
[ https://issues.apache.org/jira/browse/DERBY-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569559#action_12569559 ] Dyre Tjeldvoll commented on DERBY-3301: --- Thanks for confirming Craig. I'm planning to merge it to 10.3. I just need to run the tests before I can commit the merge. After that I think it is OK to close it. Incorrect result from query with nested EXIST - Key: DERBY-3301 URL: https://issues.apache.org/jira/browse/DERBY-3301 Project: Derby Issue Type: Bug Components: SQL Affects Versions: 10.1.3.1, 10.2.1.6, 10.3.2.1 Reporter: Craig Russell Assignee: Thomas Nielsen Fix For: 10.4.0.0 Attachments: d3301-queryplan.log, derby-3301-1.diff, derby-3301-1.stat, derby-3301-2.diff, derby-3301-3.diff, derby-3301-3b.diff, derby-3301-4.diff, derby-3301-4b.diff, derby-3301-4b.stat, derby-3301-4c.diff, derby-3301-5.diff, derby-3301-6.diff, derby-3301-7.diff, derby-3301-8.diff, derby-3301-extra.sql, derby-3301-test-1.diff, derby-3301-test-1.stat, derby-3301-test-2.diff, derby-3301-test-3.diff, derby-3301-test-3.stat, derby-3301-test-master-2.diff, derby-3301-test-master-3.diff, derby-3301-test-master-3.stat, derby-3301-test-master.diff, derby-3301-test-master.stat, derby-3301.sql Derby returns unexpected results from a query with embedded EXIST clauses. The query SQL is generated by the JPOX jdo implementation and is supposed to return all of the PERSONS and PROJECTS where there is an entry in the join table. This query works as expected when using MySQL. Here's the query: SELECT UNBOUND_E.PERSONID, UNBOUND_P.PROJID FROM applicationidentity0.DEPARTMENTS THIS, applicationidentity0.PERSONS UNBOUND_E, applicationidentity0.PROJECTS UNBOUND_P WHERE EXISTS ( SELECT 1 FROM applicationidentity0.PERSONS THIS_EMPLOYEES_E WHERE EXISTS ( SELECT 1 FROM applicationidentity0.PROJECT_MEMBER THIS_EMPLOYEES_E_PROJECTS_P WHERE THIS_EMPLOYEES_E_PROJECTS_P.MEMBER = THIS_EMPLOYEES_E.PERSONID AND THIS_EMPLOYEES_E_PROJECTS_P.MEMBER = THIS_EMPLOYEES_E.PERSONID AND THIS_EMPLOYEES_E.DEPARTMENT = THIS.ID AND THIS_EMPLOYEES_E.DEPARTMENT = THIS.ID AND UNBOUND_P.PROJID = THIS_EMPLOYEES_E_PROJECTS_P.PROJID AND UNBOUND_E.PERSONID = THIS_EMPLOYEES_E.PERSONID) ); PERSONID |PROJID --- 3 |1 5 |3 4 |3 2 |1 1 |1 5 rows selected I'm expecting 7 rows to be returned here, one row for each row in the join table. Here's the schema: CREATE TABLE departments ( ID INTEGER NOT NULL, NAME VARCHAR(32) NOT NULL, EMP_OF_THE_MONTH INTEGER, COMPANYID INTEGER, DISCRIMINATOR VARCHAR(255), CONSTRAINT DEPTS_COMP_FK FOREIGN KEY (COMPANYID) REFERENCES companies, CONSTRAINT DEPTS_PK PRIMARY KEY (ID) ); CREATE TABLE persons ( PERSONID INTEGER NOT NULL, FIRSTNAME VARCHAR(32) NOT NULL, LASTNAME VARCHAR(32) NOT NULL, MIDDLENAME VARCHAR(32), BIRTHDATE TIMESTAMP NOT NULL, ADDRID INTEGER, STREET VARCHAR(64), CITY VARCHAR(64), STATE CHAR(2), ZIPCODE CHAR(5), COUNTRY VARCHAR(64), HIREDATE TIMESTAMP, WEEKLYHOURS REAL, DEPARTMENT INTEGER, FUNDINGDEPT INTEGER, MANAGER INTEGER, MENTOR INTEGER, HRADVISOR INTEGER, SALARY REAL, WAGE REAL, DISCRIMINATOR varchar(255) NOT NULL, CONSTRAINT PERS_DEPT_FK FOREIGN KEY (DEPARTMENT) REFERENCES departments, CONSTRAINT PERS_FUNDDEPT_FK FOREIGN KEY (FUNDINGDEPT) REFERENCES departments, CONSTRAINT PERS_MANAGER_FK FOREIGN KEY (MANAGER) REFERENCES persons, CONSTRAINT PERS_MENTOR_FK FOREIGN KEY (MENTOR) REFERENCES persons, CONSTRAINT PERS_HRADVISOR_FK FOREIGN KEY (HRADVISOR) REFERENCES persons, CONSTRAINT EMPS_PK PRIMARY KEY (PERSONID) ); CREATE TABLE projects ( PROJID INTEGER NOT NULL, NAME VARCHAR(32) NOT NULL, BUDGET DECIMAL(11,2) NOT NULL, DISCRIMINATOR VARCHAR(255), CONSTRAINT PROJS_PK PRIMARY KEY (PROJID) ); CREATE TABLE project_member ( PROJID INTEGER REFERENCES projects NOT NULL, MEMBER INTEGER REFERENCES persons NOT NULL ); ij connect 'jdbc:derby:/Users/clr/apache/jdo/trunk/tck2/target/database/derby/jdotckdb'; ij set schema applicationidentity0; 0 rows inserted/updated/deleted ij select * from persons; PERSONID |FIRSTNAME |LASTNAME |MIDDLENAME |BIRTHDATE |ADDRID |STREET |CITY |STA|ZIPC|COUNTRY
[jira] Commented: (DERBY-3375) Localize new error messages added in 10.3
[ https://issues.apache.org/jira/browse/DERBY-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569574#action_12569574 ] Knut Anders Hatlen commented on DERBY-3375: --- I think it's better to have language as an attribute. Something like this: msg name42Y26/name text lang=enAggregates are not allowed in the GROUP BY list./text text lang=de_DEAggregate sind in der ''GROUP BY''-Liste nicht zulässig./text text lang=frLes agrégats ne sont pas autorisés dans la liste GROUP BY./text ... /msg Localize new error messages added in 10.3 - Key: DERBY-3375 URL: https://issues.apache.org/jira/browse/DERBY-3375 Project: Derby Issue Type: Improvement Components: Localization Affects Versions: 10.3.2.1 Reporter: Dyre Tjeldvoll Priority: Minor Fix For: 10.4.0.0 Attachments: CheckMessages.java, checkMessages.sql, derby-3375.diff, drda_messages.zip, engine_messages.zip New error messages added in 10.3 have not been localized. Should translate these into as many languages as possible. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3326) Introduce a caching logical connection and logical prepared statement in the client driver
[ https://issues.apache.org/jira/browse/DERBY-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Waagan updated DERBY-3326: --- Attachment: derby-3326-3b-new_classes.stat derby-3326-3b-new_classes.diff 'derby-3326-3b-new_classes.diff' is a new version with changes in LogicalStatementEntity and a test. The test is a package private test, and can be built and run with 'ant pptesting junit-pptesting'. It is hard to write a proper normal test, as statement pooling is supposed to be transparent to the user and there are no methods to obtain information about the cache itself etc. The only ideas I have come up with so far, is making sure it is enabled (by checking implementation details, like which class is used), and making sure nothing fails if you overflow the cache etc. To test the logical forwarding classes, I will identify some suitable existing tests and run them with a connection pool data source decorator. Introduce a caching logical connection and logical prepared statement in the client driver -- Key: DERBY-3326 URL: https://issues.apache.org/jira/browse/DERBY-3326 Project: Derby Issue Type: Sub-task Components: JDBC, Network Client Affects Versions: 10.4.0.0 Reporter: Kristian Waagan Assignee: Kristian Waagan Fix For: 10.4.0.0 Attachments: derby-3326-1a_cpds_testing_preparation.diff, derby-3326-1a_cpds_testing_preparation.stat, derby-3326-1b_cpds_testing_preparation.diff, derby-3326-2a-method_rename.diff, derby-3326-3a-new_classes.diff, derby-3326-3a-new_classes.stat, derby-3326-3b-new_classes.diff, derby-3326-3b-new_classes.stat A logical connection with statement caching capabilities is required to support JDBC prepared statement pooling. Further, a logical prepared statement object is also needed. The logical prepared statements will be generated by the logical connection's 'prepareStatement'-method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3422) Embedded returns wrong value for DatabaseMetaData.autoCommitFailureClosesAllResultSets()
[ https://issues.apache.org/jira/browse/DERBY-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-3422: -- Derby Info: [Patch Available] Embedded returns wrong value for DatabaseMetaData.autoCommitFailureClosesAllResultSets() Key: DERBY-3422 URL: https://issues.apache.org/jira/browse/DERBY-3422 Project: Derby Issue Type: Bug Components: JDBC Affects Versions: 10.4.0.0 Reporter: Knut Anders Hatlen Assignee: Knut Anders Hatlen Priority: Minor Attachments: d3422.diff, d3422.stat, test.diff DatabaseMetaData.autoCommitFailureClosesAllResultSets() returns false both on the client and on embedded. However, the embedded driver does in fact close all open result sets when an error occurs in auto-commit mode. There is a test case in jdbc4.TestDbMetaData to test this (testAutoCommitFailure), but it only uses ResultSet.isClosed() to check whether or not the result set is closed after the failure. Because of DERBY-3404, isClosed() returns false for the result sets that have been closed because of the failure, so the test doesn't reveal the bug. If the test is changed to invoke methods on the result set (e.g. next()) instead of calling isClosed(), we'll see that the result set is in fact closed and get an SQLException with SQL state XCL16. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3422) Embedded returns wrong value for DatabaseMetaData.autoCommitFailureClosesAllResultSets()
[ https://issues.apache.org/jira/browse/DERBY-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-3422: -- Attachment: d3422.stat d3422.diff Attached is a patch that changes the return value for EmbedDatabaseMetadata40.autoCommitFailureClosesAllResultSets() and updates TestDbMetaData. When this patch is applied, autoCommitFailureClosesAllResultSets() returns different values on embedded and on the client, so if the approach is accepted and the patch is committed, we should also file an issue to track the difference between client and embedded. Embedded returns wrong value for DatabaseMetaData.autoCommitFailureClosesAllResultSets() Key: DERBY-3422 URL: https://issues.apache.org/jira/browse/DERBY-3422 Project: Derby Issue Type: Bug Components: JDBC Affects Versions: 10.4.0.0 Reporter: Knut Anders Hatlen Assignee: Knut Anders Hatlen Priority: Minor Attachments: d3422.diff, d3422.stat, test.diff DatabaseMetaData.autoCommitFailureClosesAllResultSets() returns false both on the client and on embedded. However, the embedded driver does in fact close all open result sets when an error occurs in auto-commit mode. There is a test case in jdbc4.TestDbMetaData to test this (testAutoCommitFailure), but it only uses ResultSet.isClosed() to check whether or not the result set is closed after the failure. Because of DERBY-3404, isClosed() returns false for the result sets that have been closed because of the failure, so the test doesn't reveal the bug. If the test is changed to invoke methods on the result set (e.g. next()) instead of calling isClosed(), we'll see that the result set is in fact closed and get an SQLException with SQL state XCL16. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3421) Remove unused code for caching of connect bytes
[ https://issues.apache.org/jira/browse/DERBY-3421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569583#action_12569583 ] Knut Anders Hatlen commented on DERBY-3421: --- +1 to commit. It doesn't sound like an important feature, and if someone thinks it is, they can always get the code back from svn and do what it takes to enable it. Since it's not used now, it's better to remove it so that the code is easier to understand. I think you can also remove NetConnectionReply.verifyDeferredReset() since you removed the only code that calls it. Remove unused code for caching of connect bytes --- Key: DERBY-3421 URL: https://issues.apache.org/jira/browse/DERBY-3421 Project: Derby Issue Type: Improvement Components: Network Client Affects Versions: 10.4.0.0 Reporter: Kristian Waagan Assignee: Kristian Waagan Priority: Minor Attachments: derby-3421-1a-removal.diff, derby-3421-1a-removal.stat The client driver has code for caching connect bytes, but it is not used. This unused code clutters the rest of the code and makes it harder to understand. Secondly, the variable used to determine if the cached connect bytes can be used is public in am.Connection. If someone has historic information about this feature, it would be nice if they could add the information to this Jira. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Subscription: Derby: JIRA issues with patch available
Issue Subscription
Filter: Derby: JIRA issues with patch available (20 issues)
Subscriber: derby-dev
Key Summary
DERBY-3422 Embedded returns wrong value for
DatabaseMetaData.autoCommitFailureClosesAllResultSets()
https://issues.apache.org/jira/browse/DERBY-3422
DERBY-3421 Remove unused code for caching of connect bytes
https://issues.apache.org/jira/browse/DERBY-3421
DERBY-3326 Introduce a caching logical connection and logical prepared
statement in the client driver
https://issues.apache.org/jira/browse/DERBY-3326
DERBY-3349 Nested WHERE EXISTS queries need improved testing
https://issues.apache.org/jira/browse/DERBY-3349
DERBY-3303 ArrayIndexOutOfBoundsException at MergeSort.compare
https://issues.apache.org/jira/browse/DERBY-3303
DERBY-3299 Uniqueness violation error (23505) occurs after dropping a PK
constraint if there exists a foreign key on the same columns.
https://issues.apache.org/jira/browse/DERBY-3299
DERBY-3329 Enable statement pooling in the client JDBC driver
https://issues.apache.org/jira/browse/DERBY-3329
DERBY-3328 Extend client JDBC object factory with methods to create objects
required for statement pooling
https://issues.apache.org/jira/browse/DERBY-3328
DERBY-3382 Replication: Slave must inform master if DBs are out of sync.
https://issues.apache.org/jira/browse/DERBY-3382
DERBY-2559 recreating a datasource using javax.naming.Reference from a
ClientDataSource40 fails
https://issues.apache.org/jira/browse/DERBY-2559
DERBY-3379 No Current connection on PooledConnection.getConnection() if
pooled connection is reused during connectionClosed processing
https://issues.apache.org/jira/browse/DERBY-3379
DERBY-3014 Make
SYSCS_UTIL.SYSCS_GET_DATABASE_PROPERTY('derby.user.username') return NULL
instead of the hash value of the password
https://issues.apache.org/jira/browse/DERBY-3014
DERBY-1824 Permission/privlege names in exceptions should be in upper case as
keywords, not lower case.
https://issues.apache.org/jira/browse/DERBY-1824
DERBY-3001 SYSTABLES documentation for TABLETYPE should include 'A' (Synonym)
https://issues.apache.org/jira/browse/DERBY-3001
DERBY-3409 Remove JDBC 2.0-specific topics from Reference Manual and merge
implementation notes as needed
https://issues.apache.org/jira/browse/DERBY-3409
DERBY-3205 Replication: Add connection url command options for starting,
stopping slave and for failover
https://issues.apache.org/jira/browse/DERBY-3205
DERBY-2871 XATransactionTest gets XaException: Error executing a
XAResource.commit(), server returned XAER_PROTO.
https://issues.apache.org/jira/browse/DERBY-2871
DERBY-2954 Add commands to NetworkServerControl for interacting with the
replication functionality
https://issues.apache.org/jira/browse/DERBY-2954
DERBY-2953 Dump the information about rollbacks of the global transaction
(introduced in DERBY-2220 and DERBY-2432) to derby.log
https://issues.apache.org/jira/browse/DERBY-2953
DERBY-3227 Remove final from all getConnection() methods in EmbeddedDataSource
https://issues.apache.org/jira/browse/DERBY-3227
[jira] Commented: (DERBY-3375) Localize new error messages added in 10.3
[ https://issues.apache.org/jira/browse/DERBY-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569575#action_12569575 ] Knut Anders Hatlen commented on DERBY-3375: --- how do I write the resulting tree back to a new file? Could you use javax.xml.transform.Transformer? This writes an empty XML document to System.out: Transformer t = TransformerFactory.newInstance().newTransformer(); t.transform(new DOMSource(), new StreamResult(System.out)); I think you can pass Document objects to DOMSource's constructor. Localize new error messages added in 10.3 - Key: DERBY-3375 URL: https://issues.apache.org/jira/browse/DERBY-3375 Project: Derby Issue Type: Improvement Components: Localization Affects Versions: 10.3.2.1 Reporter: Dyre Tjeldvoll Priority: Minor Fix For: 10.4.0.0 Attachments: CheckMessages.java, checkMessages.sql, derby-3375.diff, drda_messages.zip, engine_messages.zip New error messages added in 10.3 have not been localized. Should translate these into as many languages as possible. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-1848) jdbcapi/SetQueryTimeoutTest.java fails on IBM wctme 5.7
[ https://issues.apache.org/jira/browse/DERBY-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569593#action_12569593 ] Kathey Marsden commented on DERBY-1848: --- Saw this against weme6.1 on February 16, 2008 on trunk. jdbcapi/SetQueryTimeoutTest.java fails on IBM wctme 5.7 Key: DERBY-1848 URL: https://issues.apache.org/jira/browse/DERBY-1848 Project: Derby Issue Type: Test Components: Regression Test Failure Affects Versions: 10.2.2.1, 10.3.1.4 Environment: Windows Reporter: Rajesh Kartha The following is the diff: *** Start: SetQueryTimeoutTest jdk1.3.1 subset - 2.2 derbyall:jdbcapi 2006-09-10 11:07:05 *** 7 del Statement 1 completed 8 del Statement 2 completed 9 del Statement 3 completed 10 del Testing timeout with an execute operation 11 del Statements that should time out timed out, and statements that should complete completed 12 del Testing setting a negative timeout value 13 del Negative timeout value caused exception, as expected 14 del Execute returned a ResultSet 15 del Testing that Statement remembers timeout. 16 del Testing that PreparedStatement remembers timeout. 17 del Testing that CallableStatement remembers timeout. 18 del Testing timeout with executeUpdate call. 19 del Test SetQueryTimeoutTest PASSED 19a7,11 Test SetQueryTimeoutTest FAILED org.apache.derbyTesting.functionTests.tests.jdbcapi.SetQueryTimeoutTest$TestFailedException: Unexpected exception in 1: java.sql.SQLException: The statement has been cancelled or timed out. ERROR XCL52: The statement has been cancelled or timed out. java.sql.SQLException: Invalid transaction state. java.sql.SQLException: Invalid transaction state. Test Failed. *** End: SetQueryTimeoutTest jdk1.3.1 subset - 2.2 derbyall:jdbcapi 2006-09-10 11:07:26 *** -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
a couple of javadoc warnings on trunk
[javadoc] javadoc: warning - No source files for package org.apache.derbyTesting.functionTests.testData.serializedDataSources [javadoc] C:\nightlies\main\src\opensource\java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\DataSourceSerializationTest.java:175: warning - Tag @link: reference not found: java.sql.DataSource [javadoc] 2 warnings
[jira] Updated: (DERBY-3425) J2EEDataSourceTest throws away stack trace for many errors
[ https://issues.apache.org/jira/browse/DERBY-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-3425: -- Derby Info: [Patch Available] J2EEDataSourceTest throws away stack trace for many errors -- Key: DERBY-3425 URL: https://issues.apache.org/jira/browse/DERBY-3425 Project: Derby Issue Type: Bug Components: Test Affects Versions: 10.4.0.0 Reporter: Knut Anders Hatlen Assignee: Knut Anders Hatlen Priority: Minor Attachments: stack.diff Many of the test cases in J2EEDataSourceTest call fail() from within a catch block. Instead, they should just let the exception be thrown and let JUnit handle it. This way the stack trace will be preserved. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DERBY-3425) J2EEDataSourceTest throws away stack trace for many errors
[ https://issues.apache.org/jira/browse/DERBY-3425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Knut Anders Hatlen updated DERBY-3425: -- Attachment: stack.diff The attached patch changes the test so that the stack traces are preserved. J2EEDataSourceTest throws away stack trace for many errors -- Key: DERBY-3425 URL: https://issues.apache.org/jira/browse/DERBY-3425 Project: Derby Issue Type: Bug Components: Test Affects Versions: 10.4.0.0 Reporter: Knut Anders Hatlen Assignee: Knut Anders Hatlen Priority: Minor Attachments: stack.diff Many of the test cases in J2EEDataSourceTest call fail() from within a catch block. Instead, they should just let the exception be thrown and let JUnit handle it. This way the stack trace will be preserved. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DERBY-3425) J2EEDataSourceTest throws away stack trace for many errors
J2EEDataSourceTest throws away stack trace for many errors -- Key: DERBY-3425 URL: https://issues.apache.org/jira/browse/DERBY-3425 Project: Derby Issue Type: Bug Components: Test Affects Versions: 10.4.0.0 Reporter: Knut Anders Hatlen Assignee: Knut Anders Hatlen Priority: Minor Attachments: stack.diff Many of the test cases in J2EEDataSourceTest call fail() from within a catch block. Instead, they should just let the exception be thrown and let JUnit handle it. This way the stack trace will be preserved. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Regression Test Report - Daily 628123 - Sun DBTG
[Auto-generated mail] *Daily* 628123/2008-02-15 18:01:11 MET Failed TestsOK Skip Duration Suite --- *Jvm: 1.6* lin 0271271 071.88% derbyall 01022610226 0 1374.39% suitesAll linN+1 0271271 0 103.34% derbyall 01022610226 0 112.34% suitesAll sles 0271271 071.25% derbyall 01022610226 0 860.28% suitesAll sol 0271271 075.77% derbyall 01022610226 0 1650.90% suitesAll solN+1 0271271 096.82% derbyall 01022610226 0 203.20% suitesAll sparc 0271271 065.48% derbyall 01022610226 0 359.44% suitesAll vista 0271271 093.14% derbyall 091739173 067.04% suitesAll w2003 0271271 095.87% derbyall 091739173 0 132.24% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/testing/Limited/testSummary-628123.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.6/FailReports/628123_bySig.html *Jvm: 1.5* lin 0272272 071.35% derbyall 085088508 0 888.59% suitesAll linN+1 0272272 097.60% derbyall 085088508 0 116.29% suitesAll sles 0272272 070.50% derbyall 085088508 0 575.79% suitesAll sol 0272272 079.52% derbyall 085088508 0 851.60% suitesAll solN+1 0272272 088.07% derbyall 085088508 0 807.11% suitesAll sparc 0272272 066.28% derbyall 085088508 0 697.26% suitesAll vista 0272272 071.38% derbyall 074557455 0 395.15% suitesAll w2003 0272272 073.99% derbyall 074557455 0 258.12% suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-628123.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.5/FailReports/628123_bySig.html *Jvm: 1.4* lin NA NA NANA derbyall NA NA NANA suitesAll linN+1 NA NA NANA derbyall NA NA NANA suitesAll sles NA NA NANA derbyall NA NA NANA suitesAll sol NA NA NANA derbyall NA NA NANA suitesAll solN+1 NA NA NANA derbyall NA NA NANA suitesAll sparc NA NA NANA derbyall NA NA NANA suitesAll vista NA NA NANA derbyall NA NA NANA suitesAll w2003 NA NA NANA derbyall NA NA NANA suitesAll Details in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/testing/Limited/testSummary-628123.html Attempted failure analysis in http://dbtg.thresher.com/derby/test/Daily/jvm1.4/FailReports/628123_bySig.html --- Changes in http://dbtg.thresher.com/derby/test/Daily/UpdateInfo/628123.txt ( All results in http://dbtg.thresher.com/derby/test/ )
[jira] Commented: (DERBY-2653) Expose existing auto-generated key functionality through more JDBC APIs in Derby Client.
[ https://issues.apache.org/jira/browse/DERBY-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569606#action_12569606 ] Kathey Marsden commented on DERBY-2653: --- I checked the JCC which doesn't support columnIndexes, but does support columnNames and it ignores columns that are not identity columns for columnNames. I suggest we change the embedded driver to do the same and not throw an error if the user specifies columns that are not identity columns. Then the client can do the same. Kathey Expose existing auto-generated key functionality through more JDBC APIs in Derby Client. Key: DERBY-2653 URL: https://issues.apache.org/jira/browse/DERBY-2653 Project: Derby Issue Type: Improvement Components: JDBC Environment: Runnning with Derby Client. Reporter: A B Priority: Minor Attachments: derby-2653_proto_diff.txt See DERBY-2631 for details. Desired functionality is the same as for DERBY-2631, except that this issue is specifically for Derby Client (DERBY-2631 only addressed embedded mode). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2653) Expose existing auto-generated key functionality through more JDBC APIs in Derby Client.
[
https://issues.apache.org/jira/browse/DERBY-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569608#action_12569608
]
Kathey Marsden commented on DERBY-2653:
---
Actually I was mistaken, with columnNames with JCC against DB2, it actually
returns the insert values for both columns whether they are identity columns or
not. For example for:
s.executeUpdate(
create table t31_AutoGen (c31 int, +
c32 int generated always as identity (increment by 1), +
c33 int default 2));
String[] columnNames = {C32,C31};
PreparedStatement ps = conn.prepareStatement(insert into t31_AutoGen
values(1,DEFAULT,DEFAULT),columnNames);
ps.executeUpdate();
ResultSet rs = ps.getGeneratedKeys();
The ResultSet has 1 row with two columns, with values 1, 1.
I don't think that's right actually, but it doesn't support my argument that we
ignore non-identity columns. It would be interesting to see how other
databases behave.
Kathey
Expose existing auto-generated key functionality through more JDBC APIs in
Derby Client.
Key: DERBY-2653
URL: https://issues.apache.org/jira/browse/DERBY-2653
Project: Derby
Issue Type: Improvement
Components: JDBC
Environment: Runnning with Derby Client.
Reporter: A B
Priority: Minor
Attachments: derby-2653_proto_diff.txt
See DERBY-2631 for details. Desired functionality is the same as for
DERBY-2631, except that this issue is specifically for Derby Client
(DERBY-2631 only addressed embedded mode).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2653) Expose existing auto-generated key functionality through more JDBC APIs in Derby Client.
[ https://issues.apache.org/jira/browse/DERBY-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569612#action_12569612 ] Daniel John Debrunner commented on DERBY-2653: -- One approach might be to only accept one column arrays and then document something like: The one element column name or position array is ignored currently and the value returned corresponds to the identity column. To ensure compatibility with future changes an application should ensure the column described is the identity column. If the column name or position corresponds to another column then future changes may result in a value for a different column being returned. Expose existing auto-generated key functionality through more JDBC APIs in Derby Client. Key: DERBY-2653 URL: https://issues.apache.org/jira/browse/DERBY-2653 Project: Derby Issue Type: Improvement Components: JDBC Environment: Runnning with Derby Client. Reporter: A B Priority: Minor Attachments: derby-2653_proto_diff.txt See DERBY-2631 for details. Desired functionality is the same as for DERBY-2631, except that this issue is specifically for Derby Client (DERBY-2631 only addressed embedded mode). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (DERBY-2653) Expose existing auto-generated key functionality through more JDBC APIs in Derby Client.
[ https://issues.apache.org/jira/browse/DERBY-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569612#action_12569612 ] djd edited comment on DERBY-2653 at 2/16/08 1:27 PM: --- One approach might be to only accept one column arrays and then document something like: The one element column name or position array is ignored currently and the value returned corresponds to the identity column. To ensure compatibility with future changes an application should ensure the column described is the identity column. If the column name or position corresponds to another column or a non-existent column then future changes may result in a value for a different column being returned or an exception being thrown. [edit - add possibility for an error in the future] was (Author: djd): One approach might be to only accept one column arrays and then document something like: The one element column name or position array is ignored currently and the value returned corresponds to the identity column. To ensure compatibility with future changes an application should ensure the column described is the identity column. If the column name or position corresponds to another column then future changes may result in a value for a different column being returned. Expose existing auto-generated key functionality through more JDBC APIs in Derby Client. Key: DERBY-2653 URL: https://issues.apache.org/jira/browse/DERBY-2653 Project: Derby Issue Type: Improvement Components: JDBC Environment: Runnning with Derby Client. Reporter: A B Priority: Minor Attachments: derby-2653_proto_diff.txt See DERBY-2631 for details. Desired functionality is the same as for DERBY-2631, except that this issue is specifically for Derby Client (DERBY-2631 only addressed embedded mode). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2653) Expose existing auto-generated key functionality through more JDBC APIs in Derby Client.
[ https://issues.apache.org/jira/browse/DERBY-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569613#action_12569613 ] Kathey Marsden commented on DERBY-2653: --- Do you think we should make embedded behave the same way or just leave it as it is? Expose existing auto-generated key functionality through more JDBC APIs in Derby Client. Key: DERBY-2653 URL: https://issues.apache.org/jira/browse/DERBY-2653 Project: Derby Issue Type: Improvement Components: JDBC Environment: Runnning with Derby Client. Reporter: A B Priority: Minor Attachments: derby-2653_proto_diff.txt See DERBY-2631 for details. Desired functionality is the same as for DERBY-2631, except that this issue is specifically for Derby Client (DERBY-2631 only addressed embedded mode). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2653) Expose existing auto-generated key functionality through more JDBC APIs in Derby Client.
[ https://issues.apache.org/jira/browse/DERBY-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569614#action_12569614 ] Daniel John Debrunner commented on DERBY-2653: -- Isn't embedded doing the logical thing, checking the column is correct? If so why would we regress it? Expose existing auto-generated key functionality through more JDBC APIs in Derby Client. Key: DERBY-2653 URL: https://issues.apache.org/jira/browse/DERBY-2653 Project: Derby Issue Type: Improvement Components: JDBC Environment: Runnning with Derby Client. Reporter: A B Priority: Minor Attachments: derby-2653_proto_diff.txt See DERBY-2631 for details. Desired functionality is the same as for DERBY-2631, except that this issue is specifically for Derby Client (DERBY-2631 only addressed embedded mode). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DERBY-3426) Remove unused code for autogenerated keys columnNames
Remove unused code for autogenerated keys columnNames - Key: DERBY-3426 URL: https://issues.apache.org/jira/browse/DERBY-3426 Project: Derby Issue Type: Sub-task Components: Network Client Affects Versions: 10.4.0.0 Reporter: Kathey Marsden Assignee: Kathey Marsden Priority: Minor There is unused code for autogenerated keys that processes columnNames by flowing a select from final table statement to the server. This syntax is not supported or used by Derby and should be removed from client. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-3375) Localize new error messages added in 10.3
[ https://issues.apache.org/jira/browse/DERBY-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569651#action_12569651 ] Andrew McIntyre commented on DERBY-3375: Since you're generating an almost completely new XML file to hold all the messages, have you thought about transforming it to a standard XML format for translation, such as TMX or XLIFF? http://www.lisa.org/standards/tmx/ http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html Probably not a big deal unless the translators you are working with use tools that support one of those formats, but thought I would mention it. Localize new error messages added in 10.3 - Key: DERBY-3375 URL: https://issues.apache.org/jira/browse/DERBY-3375 Project: Derby Issue Type: Improvement Components: Localization Affects Versions: 10.3.2.1 Reporter: Dyre Tjeldvoll Priority: Minor Fix For: 10.4.0.0 Attachments: CheckMessages.java, checkMessages.sql, derby-3375.diff, drda_messages.zip, engine_messages.zip New error messages added in 10.3 have not been localized. Should translate these into as many languages as possible. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
