[jira] [Commented] (JUDDI-1011) MS SQL Server table - length of field too large
[ https://issues.apache.org/jira/browse/JUDDI-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167958#comment-17167958 ] Steve Luisser commented on JUDDI-1011: -- We are running it on MS SQL Server 2016 using the initial DB script. To get the script to run, we changed the data type for instance_parms to varchar(MAX). It seems to be working properly. Can you elaborate on some of the other fields that you are having issues with? > 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)
[jira] [Commented] (JUDDI-1011) MS SQL Server table - length of field too large
[ https://issues.apache.org/jira/browse/JUDDI-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17156717#comment-17156717 ] Steve Luisser commented on JUDDI-1011: -- When you run the command to create table j3_tmodel_instance_info on Microsoft SQL Server you get the following error message: Msg 131, Level 15, State 2, Line 1 The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000). > 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)
[jira] [Commented] (JUDDI-1011) MS SQL Server table - length of field too large
[ https://issues.apache.org/jira/browse/JUDDI-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17156157#comment-17156157 ] Alex O'Ree commented on JUDDI-1011: --- updating hibernate + using the ddl generator for newer versions of mssql, it does in fact use varchar(max) now. I found a few other fields that may have similar issues. This caused a few other unexpected issues with running queries on those fields. see the linked Jira for more information. > 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)
[jira] [Commented] (JUDDI-1011) MS SQL Server table - length of field too large
[ https://issues.apache.org/jira/browse/JUDDI-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
