[
https://issues.apache.org/jira/browse/JUDDI-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155816#comment-17155816
]
Alex O'Ree commented on JUDDI-1011:
-----------------------------------
unfortunately the reason for the 8192 value was the UDDIv3 spec itself. While
we can deviate from the spec, I'd rather not. I've linked a few other related
tickets.
In JUDDI-999 was to add the @Lob annotation which should have change the column
to some kind of blob. I'll check on the DDL generator. We are using a slightly
older version of hibernate to make the scripts. A newer version may fix it.
They may also have dialects for a newer version of mssql now too
> MS SQL Server table - length of field too large
> -----------------------------------------------
>
> Key: JUDDI-1011
> URL: https://issues.apache.org/jira/browse/JUDDI-1011
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Reporter: Steve Luisser
> Priority: Major
>
> File mssql2000.ddl
>
> create table j3_tmodel_instance_info (id numeric(19,0) not null,
> instance_parms varchar(8192), tmodel_key varchar(255) not null, entity_key
> varchar(255) not null, primary key (id));
>
> The instance_parms column exceeds the maximum length of a varchar field in
> SQL Server of 8000 characters. I’ve reviewed the scripts for the other
> database engines and the best option is to define this column as
> instance_parms varchar(max). Another option is to define this column as
> instance_parms varchar(8000) although if there was a good reason to make it
> 8192 this value could overflow.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
