[
https://issues.apache.org/jira/browse/JUDDI-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155812#comment-17155812
]
ASF subversion and git services commented on JUDDI-1015:
--------------------------------------------------------
Commit 7d562f926b974d46b5e0f9e76d774a10ff9dc889 in juddi's branch
refs/heads/bug/JUDDI-1015 from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=7d562f9 ]
JUDDI-1015 incomplete fix for certain columns being too long on specific
database vendors (oracle in this case). this has some test failures and query
issues due to the column type changes.
> Oracle database start up issue due to max string length
> -------------------------------------------------------
>
> Key: JUDDI-1015
> URL: https://issues.apache.org/jira/browse/JUDDI-1015
> Project: jUDDI
> Issue Type: Bug
> Reporter: Alex O'Ree
> Assignee: Alex O'Ree
> Priority: Major
> Fix For: 3.3.8
>
>
> from the juddi mailing list
>
> {color:#172b4d}Oracle Version of Juddi Due to string limit for a column
> CREATE TABLE j3_binding_template (entity_key VARCHAR2(255) NOT NULL,
> access_point_type VARCHAR2(255), access_point_url VARCHAR2(4096),
> hosting_redirector VARCHAR2(255), service_key VARCHAR2(255) NOT NULL, PRIMARY
> KEY (entity_key)) {color}*Oracle max varchar limit: 4000*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
