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/07/23 07:09:14 UTC
[jira] Resolved: (JUDDI-266) update ingres create_database.sql
script
[ https://issues.apache.org/jira/browse/JUDDI-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Cunningham resolved JUDDI-266.
----------------------------------
Resolution: Fixed
Applied the v2 diff patch specified here.
> update ingres create_database.sql script
> ----------------------------------------
>
> Key: JUDDI-266
> URL: https://issues.apache.org/jira/browse/JUDDI-266
> Project: jUDDI
> Issue Type: Improvement
> Affects Versions: 2.0rc6, 2.0rc7
> Environment: N/A
> Reporter: murray armfield
> Assignee: Tom Cunningham
> Fix For: 2.0
>
> Attachments: apache-juddi-2.0rc7-ingres-v2.diff, apache-juddi-2.0rc7-ingres.diff
>
> Original Estimate: 0.17h
> Remaining Estimate: 0.17h
>
> I've created a patch to update the create_database.sql script for ingres. I initially used the postgresl create_database.sql script to write the ingres version, however it seems that the postgresql one is not quite as good as many of the others. This patch for the ingres create_database.sql script makes the ingres version identical to the db2, derby, oracle and mysql versions, other than the ingres specific bits of course.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.