[jira] Reopened: (DERBY-989) unit/daemonService.unit fails intermittently: 'ran out of time'
[ http://issues.apache.org/jira/browse/DERBY-989?page=all ] Knut Anders Hatlen reopened DERBY-989: -- unit/daemonService.unit fails intermittently: 'ran out of time' --- Key: DERBY-989 URL: http://issues.apache.org/jira/browse/DERBY-989 Project: Derby Issue Type: Test Components: Regression Test Failure Affects Versions: 10.2.1.6, 10.1.3.2 Environment: OS: Solaris 10 3/05 s10_74L2a X86 - SunOS 5.10 Generic, JVM: Sun Microsystems Inc. 1.5.0_04 OS: Solaris 9 9/04 s9s_u7wos_09 SPARC - SunOS 5.9 Generic_118558-11, JVM: Sun Microsystems Inc. 1.5.0_03 OS: Red Hat Enterprise Linux AS release 3 (Taroon Update 4) - Linux 2.4.21-27.ELsmp #1 SMP Wed Dec 1 21:50:31 EST 2004 GNU/Linux, JVM: Sun Microsystems Inc. 1.5.0_03 Reporter: Ole Solberg Assigned To: Knut Anders Hatlen Priority: Minor Fix For: 10.2.1.6 Attachments: 989-411220-derbyall_derbyall_unit_unit_derby.log, derby-989-javadoc.diff, derby-989-javadoc.stat, derby-989-testfix.diff, derby-989-testfix.stat, derby-989-timebomb.diff, derby-989-timebomb.stat, derby-989-v1.diff, derby-989-v1.stat Signature: * Diff file unit/unit/daemonService.diff *** Start: daemonService jdk1.5.0_04 unit:unit 2006-02-14 20:46:42 *** 2 del -- Unit Test T_DaemonService finished 2 add ran out of time Shutting down due to unit test failure. Exit due to time bomb Test Failed. *** End: daemonService jdk1.5.0_04 unit:unit 2006-02-14 21:47:13 *** http://www.multinet.no/~solberg/public/Apache/Derby/Limited/testSummary-377800.html [SunOS-5.10 i86pc-i386] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-989) unit/daemonService.unit fails intermittently: 'ran out of time'
[ http://issues.apache.org/jira/browse/DERBY-989?page=all ] Knut Anders Hatlen closed DERBY-989. Fix Version/s: 10.1.3.2 Resolution: Fixed Patch merged cleanly from trunk. Test passes. Committed into 10.1 with revision 463899. unit/daemonService.unit fails intermittently: 'ran out of time' --- Key: DERBY-989 URL: http://issues.apache.org/jira/browse/DERBY-989 Project: Derby Issue Type: Test Components: Regression Test Failure Affects Versions: 10.2.1.6, 10.1.3.2 Environment: OS: Solaris 10 3/05 s10_74L2a X86 - SunOS 5.10 Generic, JVM: Sun Microsystems Inc. 1.5.0_04 OS: Solaris 9 9/04 s9s_u7wos_09 SPARC - SunOS 5.9 Generic_118558-11, JVM: Sun Microsystems Inc. 1.5.0_03 OS: Red Hat Enterprise Linux AS release 3 (Taroon Update 4) - Linux 2.4.21-27.ELsmp #1 SMP Wed Dec 1 21:50:31 EST 2004 GNU/Linux, JVM: Sun Microsystems Inc. 1.5.0_03 Reporter: Ole Solberg Assigned To: Knut Anders Hatlen Priority: Minor Fix For: 10.1.3.2, 10.2.1.6 Attachments: 989-411220-derbyall_derbyall_unit_unit_derby.log, derby-989-javadoc.diff, derby-989-javadoc.stat, derby-989-testfix.diff, derby-989-testfix.stat, derby-989-timebomb.diff, derby-989-timebomb.stat, derby-989-v1.diff, derby-989-v1.stat Signature: * Diff file unit/unit/daemonService.diff *** Start: daemonService jdk1.5.0_04 unit:unit 2006-02-14 20:46:42 *** 2 del -- Unit Test T_DaemonService finished 2 add ran out of time Shutting down due to unit test failure. Exit due to time bomb Test Failed. *** End: daemonService jdk1.5.0_04 unit:unit 2006-02-14 21:47:13 *** http://www.multinet.no/~solberg/public/Apache/Derby/Limited/testSummary-377800.html [SunOS-5.10 i86pc-i386] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1942) There exists difference between behavior of setNull(Types.TIME) and setTiime(null).
[ http://issues.apache.org/jira/browse/DERBY-1942?page=all ] Tomohito Nakayama updated DERBY-1942: - Attachment: DERBY-1942.patch * Description of the patch * Make it impossible to assign TIME type value to TIMESTAMP variable in order to unify the behavior of setNull(Types.TIME) and setTime(null). * Result of the test * Executed derbyall and found only intermittent error in derbynet/testSecMec.java. There exists difference between behavior of setNull(Types.TIME) and setTiime(null). Key: DERBY-1942 URL: http://issues.apache.org/jira/browse/DERBY-1942 Project: Derby Issue Type: Bug Components: JDBC Reporter: Tomohito Nakayama Assigned To: Tomohito Nakayama Attachments: DERBY-1942.patch The result of setNull(java.sql.Types.TIME) for TIMESTAMP typed variable is regarded as error. However, the result of setTime(null) for TIMESTAMP typed variable is not regarded as error . see http://issues.apache.org/jira/browse/DERBY-1610#action_12436554 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1689) Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3
[ http://issues.apache.org/jira/browse/DERBY-1689?page=comments#action_12442302 ] Bryan Pendleton commented on DERBY-1689: Deepa, does this issue need to be addressed prior to committing any new trunk changes which include update functionality? For instance, there is a patch to DERBY-630 ready for commit. Will committing that patch complicate this issue? Remove Upgrade_10_1_10_2 test from 10.3 and add new upgrade tests for 10.3 -- Key: DERBY-1689 URL: http://issues.apache.org/jira/browse/DERBY-1689 Project: Derby Issue Type: Task Components: Test, Regression Test Failure Affects Versions: 10.3.0.0 Reporter: Deepa Remesh Priority: Minor Fix For: 10.3.0.0 Attachments: remove_10_2_upg_test.diff The current upgrade test Upgrade_10_1_10_2 tests upgrade from 10.1 to 10.2. This test should continue to run in 10.2 branch. It is failing in the new trunk (10.3) because the test internally checks the versions. To resolve this failure, we should remove this test from running in new trunk and then create new upgrade tests to test new upgrade scenarios: * 10.1 to 10.3 * 10.2 to 10.3 Upgrade test uses the UpgradeTester class which contains the test for various upgrade scenarios. To test any old/new release upgrade combination, we can create a new test which uses this class and pass in the old and new versions to the class. Any new upgrade scenarios for new features can be added to UpgradeTester (e.g, test for 10.2 feature grant/revoke was added to UpgradeTester). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-630) create trigger fails with null pointer exception
[ http://issues.apache.org/jira/browse/DERBY-630?page=comments#action_12442304 ] Bryan Pendleton commented on DERBY-630: --- Hi Yip, thanks very much for adding the upgrade test. It looks great, and it passes fine in my environment. However, I am wondering: should we fix DERBY-1689 first? More precisely, do you think that committing this change will make it harder to address DERBY-1689? If not, I think I'm ready to commit this patch. create trigger fails with null pointer exception Key: DERBY-630 URL: http://issues.apache.org/jira/browse/DERBY-630 Project: Derby Issue Type: Bug Components: SQL Affects Versions: 10.1.1.0 Environment: windows 2000, sun jdk 1.5.0 Reporter: mardacay Assigned To: Yip Ng Attachments: derby630-trunk-diff01.txt, derby630-trunk-diff02.txt, derby630-trunk-stat01.txt, derby630-trunk-stat02.txt When i create a brand new database, and execute the following statements all in one transaction or each of them in their own transaction, then it fails at trigger creation with null pointer exception. if i exclude the schema names from statement, then it runs fine. (If S1 is ommited from every statement then it runs fine). Once the version without the schema names run fine, i can run the version that has schema names, fine also. create schema S1; create table S1.PRODUCT( PRODUCT_ID VARCHAR(255) unique not null, VERSION BIGINT ); create table S1.CATEGORY( CAT_ID VARCHAR(255), NAME varchar(255) not null, VERSION BIGINT ); create table S1.PROD_IN_CAT( CAT_ID VARCHAR(255) not null, PRODUCT_ID VARCHAR(255) not null, VERSION BIGINT ); create trigger S1.product_v after update of version on S1.product referencing new as n for each row mode db2sql update S1.prod_in_cat set version = n.version where S1.prod_in_cat.product_id=n.product_id; java.lang.NullPointerException at org.apache.derby.impl.sql.catalog.SYSSTATEMENTSRowFactory.makeSYSSTATEMENTSrow(Unknown Source) at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addSPSDescriptor(Unknown Source) at org.apache.derby.impl.sql.execute.CreateTriggerConstantAction.createSPS(Unknown Source) at org.apache.derby.impl.sql.execute.CreateTriggerConstantAction.executeConstantAction(Unknown Source)Stopping progress indicator for: Executing SQL at org.apache.derby.impl.sql.execute.MiscResultSet.open(Unknown Source) at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Subscription: Derby: JIRA issues with patch available
Issue Subscription Filter: Derby: JIRA issues with patch available (15 issues) Subscriber: derby-dev Key Summary DERBY-630 create trigger fails with null pointer exception http://issues.apache.org/jira/browse/DERBY-630 DERBY-183 Parameter names required in CREATE FUNCTION http://issues.apache.org/jira/browse/DERBY-183 DERBY-1953 Make FOR EACH clause and MODE DB2SQL in CREATE TRIGGER statement optional http://issues.apache.org/jira/browse/DERBY-1953 DERBY-737 SYSCS_UTIL.SYSCS_COMPRESS_TABLE should create statistics if they do not exist http://issues.apache.org/jira/browse/DERBY-737 DERBY-1948 10.2 'Working with Derby' manual errors. http://issues.apache.org/jira/browse/DERBY-1948 DERBY-1839 Doc Review Updates - Ref Manual http://issues.apache.org/jira/browse/DERBY-1839 DERBY-1954 Update sysinfo output documentation in Tools and Utilities Guide http://issues.apache.org/jira/browse/DERBY-1954 DERBY-1951 Missing directory separator in path construction in 'NetworkServerTestSetup.setUp' http://issues.apache.org/jira/browse/DERBY-1951 DERBY-1938 Add support for setObject(arg, null) http://issues.apache.org/jira/browse/DERBY-1938 DERBY-1893 Convert largedata/lobLengthTests.java to junit http://issues.apache.org/jira/browse/DERBY-1893 DERBY-1930 Move JDBC implementation notes into the published javadoc http://issues.apache.org/jira/browse/DERBY-1930 DERBY-1918 INCREMENT of IDENTITY column described as allowing a value of zero in reference manual http://issues.apache.org/jira/browse/DERBY-1918 DERBY-963 Allow user friendly string values for security mechanism in client connection url. http://issues.apache.org/jira/browse/DERBY-963 DERBY-1808 [PATCH] Inbuilt functions SIGN, SQRT, RAND, RANDOM, COSH, SINH and TANH http://issues.apache.org/jira/browse/DERBY-1808 DERBY-646 In-memory backend storage support http://issues.apache.org/jira/browse/DERBY-646
Regression Test Report - 463721 - Sun DBTG
[Auto-generated mail] ** 463721/2006-10-13 18:00:07 MEST ** Failed TestsOK Skip Duration Platform --- *Jvm: 1.6* 0687687 0 106.19% lin NA NA NANA sol 0687687 097.05% solN+1 0687687 0 107.67% sparc 0687687 0 160.81% win Details in http://www.multinet.no/~solberg/public/Apache/Daily/jvm1.6/Limited/testSummary-463721.html Attempted failure analysis in http://www.multinet.no/~solberg/public/Apache/Daily/Failures/jvm1.6/463721.html *Jvm: 1.5* 0675675 2 105.22% lin NA NA NANA sol 0675675 297.18% solN+1 0675675 2 106.61% sparc 1675674 2 170.15% win Details in http://www.multinet.no/~solberg/public/Apache/Daily/jvm1.5/Limited/testSummary-463721.html Attempted failure analysis in http://www.multinet.no/~solberg/public/Apache/Daily/Failures/jvm1.5/463721.html *Jvm: 1.4* 0669669 4 105.05% lin NA NA NANA sol 0669669 497.67% solN+1 0669669 4 106.35% sparc 0669669 497.21% win Details in http://www.multinet.no/~solberg/public/Apache/Daily/jvm1.4/Limited/testSummary-463721.html Attempted failure analysis in http://www.multinet.no/~solberg/public/Apache/Daily/Failures/jvm1.4/463721.html --- Changes in http://www.multinet.no/~solberg/public/Apache/Daily/UpdateInfo/463721.txt ( All results in http://www.multinet.no/~solberg/public/Apache/Daily/index.html )
[jira] Commented: (DERBY-183) Parameter names required in CREATE FUNCTION
[ http://issues.apache.org/jira/browse/DERBY-183?page=comments#action_12442313 ] Bryan Pendleton commented on DERBY-183: --- I believe that RoutineAliasInfo.getParameterNames()[n] will return the empty string. It's a bit hard to figure this out directly, because I couldn't figure out how that method would get called from, say, an SQL statement. However, I looked at this indirectly by running dblook against a database which had some functions with unnamed parameters, and the output of dblook was as follows: CREATE FUNCTION APP.NONAME1 ( INTEGER, INTEGER) RETURNS INTEGER LANGUAGE JAVA PARAMETER STYLE JAVA READS SQL DATA CALLED ON NULL INPUT EXTERNAL NAME 'java.lang.Math.max' ; CREATE FUNCTION APP.NONAME2 (P1 INTEGER, INTEGER) RETURNS INTEGER LANGUAGE JAVA PARAMETER STYLE JAVA READS SQL DATA CALLED ON NULL INPUT EXTERNAL NAME 'java.lang.Math.max' ; By examining how RoutineAliasInfo.toString works, it seems that if the parameterNames array held NULL for the unnamed parameters, then dblook would have generated: CREATE FUNCTION APP.NONAME1 (NULL INTEGER,NULL INTEGER) RETURNS INTEGER LANGUAGE JAVA PARAMETER STYLE JAVA READS SQL DATA CALLED ON NULL INPUT EXTERNAL NAME 'java.lang.Math.max' ; CREATE FUNCTION APP.NONAME2 (P1 INTEGER,NULL INTEGER) RETURNS INTEGER LANGUAGE JAVA PARAMETER STYLE JAVA READS SQL DATA CALLED ON NULL INPUT EXTERNAL NAME 'java.lang.Math.max' ; So therefore I think that the parameterNames array contains empty strings, not null values, for unnamed parameters. I'll add a comment to this effect in the RoutineAliasInfo class. Parameter names required in CREATE FUNCTION --- Key: DERBY-183 URL: http://issues.apache.org/jira/browse/DERBY-183 Project: Derby Issue Type: Bug Components: SQL Affects Versions: 10.0.2.0 Reporter: Jack Klebanoff Assigned To: James F. Adams Priority: Minor Attachments: Derby183.patch.txt, Derby183.patch2.txt, Derby183.patch3.txt A statement like create function s2.f2( char(8), integer) returns int language java parameter style java external name 'myclass.mymethod' fails with the message ERROR 42X01: Syntax error: Encountered char at line 1, column 24 However create function s2.f2( p1 char(8), p2 integer) returns int language java parameter style java external name 'myclass.mymethod' is accepted. The Derby documentation (at http://incubator.apache.org/derby/manuals/reference/sqlj27.html#CREATE+PROCEDURE+Statement), the SQL2003 standard, and DB2 all agree that the parameter name is optional. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-183) Parameter names required in CREATE FUNCTION
[ http://issues.apache.org/jira/browse/DERBY-183?page=all ] Bryan Pendleton resolved DERBY-183. --- Fix Version/s: 10.3.0.0 Resolution: Fixed Derby Info: (was: [Patch Available]) Committed Derby183.patch3.txt, plus a comment-only change to RoutineAliasInfo.java, to subversion as revision 463982. James, thanks for the patch and for the tests and for the good comments. Could you please verify that the changes look correct to you, and then close this issue? Thanks! Parameter names required in CREATE FUNCTION --- Key: DERBY-183 URL: http://issues.apache.org/jira/browse/DERBY-183 Project: Derby Issue Type: Bug Components: SQL Affects Versions: 10.0.2.0 Reporter: Jack Klebanoff Assigned To: James F. Adams Priority: Minor Fix For: 10.3.0.0 Attachments: Derby183.patch.txt, Derby183.patch2.txt, Derby183.patch3.txt A statement like create function s2.f2( char(8), integer) returns int language java parameter style java external name 'myclass.mymethod' fails with the message ERROR 42X01: Syntax error: Encountered char at line 1, column 24 However create function s2.f2( p1 char(8), p2 integer) returns int language java parameter style java external name 'myclass.mymethod' is accepted. The Derby documentation (at http://incubator.apache.org/derby/manuals/reference/sqlj27.html#CREATE+PROCEDURE+Statement), the SQL2003 standard, and DB2 all agree that the parameter name is optional. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Doc update didn't make it to web site?
I submitted a change to fix DERBY-1926 a few days ago; the change updated ./src/ref/rrefsqlj81859.dita to add information about ALTER TABLE DROP COLUMN. I was hoping to see the change reflected at http://db.apache.org/derby/docs/dev/ref/rrefsqlj81859.html but that page still seems to be showing the prior revision of that file. Am I looking in the wrong place? Or is there something amiss with the job that pushes the updated docs to the web site? Or something amiss with my change? thanks, bryan
[jira] Reopened: (DERBY-183) Parameter names required in CREATE FUNCTION
[ http://issues.apache.org/jira/browse/DERBY-183?page=all ] James F. Adams reopened DERBY-183: -- I found through some additional testing that the previous patch has a problem for some parameter types. I have a re-worked patch that I will attach that resolves this. Parameter names required in CREATE FUNCTION --- Key: DERBY-183 URL: http://issues.apache.org/jira/browse/DERBY-183 Project: Derby Issue Type: Bug Components: SQL Affects Versions: 10.0.2.0 Reporter: Jack Klebanoff Assigned To: James F. Adams Priority: Minor Fix For: 10.3.0.0 Attachments: Derby183.patch.txt, Derby183.patch2.txt, Derby183.patch3.txt A statement like create function s2.f2( char(8), integer) returns int language java parameter style java external name 'myclass.mymethod' fails with the message ERROR 42X01: Syntax error: Encountered char at line 1, column 24 However create function s2.f2( p1 char(8), p2 integer) returns int language java parameter style java external name 'myclass.mymethod' is accepted. The Derby documentation (at http://incubator.apache.org/derby/manuals/reference/sqlj27.html#CREATE+PROCEDURE+Statement), the SQL2003 standard, and DB2 all agree that the parameter name is optional. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-183) Parameter names required in CREATE FUNCTION
[ http://issues.apache.org/jira/browse/DERBY-183?page=all ] James F. Adams updated DERBY-183: - Attachment: Derby183.patch4.txt The lookahead in the grammar of my previous patches did not work for some parameter types. I have reworked the lookahead to use syntactic lookahead similar to that used elsewhere in the grammar. I have included an additional test that would have failed with the previous patch. I have run the lang/functions.sql and lang/procedure.java using the various frameworks without error. Parameter names required in CREATE FUNCTION --- Key: DERBY-183 URL: http://issues.apache.org/jira/browse/DERBY-183 Project: Derby Issue Type: Bug Components: SQL Affects Versions: 10.0.2.0 Reporter: Jack Klebanoff Assigned To: James F. Adams Priority: Minor Fix For: 10.3.0.0 Attachments: Derby183.patch.txt, Derby183.patch2.txt, Derby183.patch3.txt, Derby183.patch4.txt A statement like create function s2.f2( char(8), integer) returns int language java parameter style java external name 'myclass.mymethod' fails with the message ERROR 42X01: Syntax error: Encountered char at line 1, column 24 However create function s2.f2( p1 char(8), p2 integer) returns int language java parameter style java external name 'myclass.mymethod' is accepted. The Derby documentation (at http://incubator.apache.org/derby/manuals/reference/sqlj27.html#CREATE+PROCEDURE+Statement), the SQL2003 standard, and DB2 all agree that the parameter name is optional. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Doc update didn't make it to web site?
Bryan Pendleton wrote: I submitted a change to fix DERBY-1926 a few days ago; the change updated ./src/ref/rrefsqlj81859.dita to add information about ALTER TABLE DROP COLUMN. I was hoping to see the change reflected at http://db.apache.org/derby/docs/dev/ref/rrefsqlj81859.html but that page still seems to be showing the prior revision of that file. Am I looking in the wrong place? Or is there something amiss with the job that pushes the updated docs to the web site? Or something amiss with my change? Hi, Bryan, I logged into people.apache.org and it looks to me like the automated doc update last succeeded on September 13 (I also checked timestamps on files in the other derby books): -bash-2.05b$ cd /www/db.apache.org/derby/docs/dev -bash-2.05b$ ls -l ref/rrefsqlj81859.html -rwxrwxr-x 1 fuzzylogic db 21042 Sep 13 23:26 ref/rrefsqlj81859.html We'll need to grab Andrew after he gets back from ApacheCon ... -jean
[jira] Resolved: (DERBY-183) Parameter names required in CREATE FUNCTION
[ http://issues.apache.org/jira/browse/DERBY-183?page=all ] Bryan Pendleton resolved DERBY-183. --- Resolution: Fixed Thanks for doing the additional testing, James, and for the updated patch. I verified that the new test cases fail without your change to the grammar, and succeed with your change to the grammar. My derbyall run was 100% clean, so I committed Derby183-patch4.txt to subversion as revision 464078. Parameter names required in CREATE FUNCTION --- Key: DERBY-183 URL: http://issues.apache.org/jira/browse/DERBY-183 Project: Derby Issue Type: Bug Components: SQL Affects Versions: 10.0.2.0 Reporter: Jack Klebanoff Assigned To: James F. Adams Priority: Minor Fix For: 10.3.0.0 Attachments: Derby183.patch.txt, Derby183.patch2.txt, Derby183.patch3.txt, Derby183.patch4.txt A statement like create function s2.f2( char(8), integer) returns int language java parameter style java external name 'myclass.mymethod' fails with the message ERROR 42X01: Syntax error: Encountered char at line 1, column 24 However create function s2.f2( p1 char(8), p2 integer) returns int language java parameter style java external name 'myclass.mymethod' is accepted. The Derby documentation (at http://incubator.apache.org/derby/manuals/reference/sqlj27.html#CREATE+PROCEDURE+Statement), the SQL2003 standard, and DB2 all agree that the parameter name is optional. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-630) create trigger fails with null pointer exception
[ http://issues.apache.org/jira/browse/DERBY-630?page=comments#action_12442368 ] Yip Ng commented on DERBY-630: -- Hi Bryan. Thanks for your continous review of the patches. If DERBY-1689 is still using the same upgrade test infrastructure, then this patch shouldn't make it harder to address the upgrade issue for 10.3. This patch has already activated the upgrade test for 10.1 to 10.3. To enable 10.2 to 10.3 upgrade test as described in DERBY-1689, the 10.2 release jars needs to be check-in to the trunk code line first. create trigger fails with null pointer exception Key: DERBY-630 URL: http://issues.apache.org/jira/browse/DERBY-630 Project: Derby Issue Type: Bug Components: SQL Affects Versions: 10.1.1.0 Environment: windows 2000, sun jdk 1.5.0 Reporter: mardacay Assigned To: Yip Ng Attachments: derby630-trunk-diff01.txt, derby630-trunk-diff02.txt, derby630-trunk-stat01.txt, derby630-trunk-stat02.txt When i create a brand new database, and execute the following statements all in one transaction or each of them in their own transaction, then it fails at trigger creation with null pointer exception. if i exclude the schema names from statement, then it runs fine. (If S1 is ommited from every statement then it runs fine). Once the version without the schema names run fine, i can run the version that has schema names, fine also. create schema S1; create table S1.PRODUCT( PRODUCT_ID VARCHAR(255) unique not null, VERSION BIGINT ); create table S1.CATEGORY( CAT_ID VARCHAR(255), NAME varchar(255) not null, VERSION BIGINT ); create table S1.PROD_IN_CAT( CAT_ID VARCHAR(255) not null, PRODUCT_ID VARCHAR(255) not null, VERSION BIGINT ); create trigger S1.product_v after update of version on S1.product referencing new as n for each row mode db2sql update S1.prod_in_cat set version = n.version where S1.prod_in_cat.product_id=n.product_id; java.lang.NullPointerException at org.apache.derby.impl.sql.catalog.SYSSTATEMENTSRowFactory.makeSYSSTATEMENTSrow(Unknown Source) at org.apache.derby.impl.sql.catalog.DataDictionaryImpl.addSPSDescriptor(Unknown Source) at org.apache.derby.impl.sql.execute.CreateTriggerConstantAction.createSPS(Unknown Source) at org.apache.derby.impl.sql.execute.CreateTriggerConstantAction.executeConstantAction(Unknown Source)Stopping progress indicator for: Executing SQL at org.apache.derby.impl.sql.execute.MiscResultSet.open(Unknown Source) at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Source) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
