[
https://issues.apache.org/jira/browse/JUDDI-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670988#action_12670988
]
Kurt T Stam commented on JUDDI-184:
-----------------------------------
Hey Tom,
I think the root cause is:
2009-02-05 21:48:44,583 ERROR [org.apache.juddi.registry.RegistryEngine] -
Could not create jUDDI database 'CURTIMESTAMP' is not recognized as a function
or procedure.
ERROR 42Y03: 'CURTIMESTAMP' is not recognized as a function or procedure.
Looks like Derby does not support CURTIMESTAMP().
> Derby db is not created correctly on initialization
> ---------------------------------------------------
>
> Key: JUDDI-184
> URL: https://issues.apache.org/jira/browse/JUDDI-184
> Project: jUDDI
> Issue Type: Bug
> Affects Versions: 2.0rc6
> Reporter: Kurt T Stam
> Assignee: Tom Cunningham
> Fix For: 2.0rc6
>
>
> When running juddi-tomcat out-of-the-box the derby database
> 1. is called juddi-derby-test-db; which we should probably change to juddi-db
> 2. when the first statement is executed in the RegistryEngine on line 302
> CREATE TABLE BUSINESS_ENTITY
> (
> BUSINESS_KEY VARCHAR(41) NOT NULL,
> AUTHORIZED_NAME VARCHAR(255) NOT NULL,
> PUBLISHER_ID VARCHAR(20) NULL,
> OPERATOR VARCHAR(255) NOT NULL,
> LAST_UPDATE TIMESTAMP NOT NULL,
> PRIMARY KEY (BUSINESS_KEY)
> )
> it throws the following exception:
> SQL Exception: Syntax error: Encountered "NULL" at line 5, column 28.
> So something is wrong when it goes to create the derby database.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
