You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Tom Cunningham (JIRA)" <ju...@ws.apache.org> on 2009/02/06 06:11:59 UTC
[jira] Resolved: (JUDDI-184) Derby db is not created correctly on
initialization
[ https://issues.apache.org/jira/browse/JUDDI-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Cunningham resolved JUDDI-184.
----------------------------------
Resolution: Fixed
Removed CURTIMESTAMP() function, changed it to CURRENT_TIME_STAMP.
> 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.