You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Olivier Dassaud (JIRA)" <ji...@codehaus.org> on 2008/03/17 12:19:47 UTC
[jira] Commented: (MRM-735) Database on MS SQL 2000/2005 fail to be
created due to too column length
[ http://jira.codehaus.org/browse/MRM-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127446 ]
Olivier Dassaud commented on MRM-735:
-------------------------------------
Hello,
In fact, there is the same problem with Oracle system... the 4000 bytes limit.
A ticket has been set and a solution is now described :
http://jira.codehaus.org/browse/MRM-657
Olivier.
> Database on MS SQL 2000/2005 fail to be created due to too column length
> ------------------------------------------------------------------------
>
> Key: MRM-735
> URL: http://jira.codehaus.org/browse/MRM-735
> Project: Archiva
> Issue Type: Bug
> Components: system
> Affects Versions: 1.0, 1.0.1
> Environment: Win XP
> Tomcat 5.5
> MS SQL 2000 / 2005
> MS SQL 2005 JDBC Driver, v1.2
> Reporter: Thomas Winkler
> Fix For: 1.0.x
>
>
> Some column lengths in the datamodel exceed the restrictions of MS SQL Server using the default String jdbc-mapping of jpox (varchar)
> These are according to package.jdo:
> - Table: ARCHIVA_PROJECT
> -> Columns: description
> - Table: ARCHIVA_LICENSES
> -> Columns: comments
> - Table: ARCHIVA_REPOSITORY_PROBLEMS
> -> Columns: message
> The 2005 Jdbc driver uses the nvarchar datatype in case of varchar jdbc types. The maximum length here would be 4000 bytes.
> Some other db systems should have the same problem, as I could see from their specs, but I'm not an expert (Oracle: 4000 bytes, DB2: 4-32k depending on page size).
> A possible fix for MS SQL is, not to provide any length. Instead we could use the jdo jdbc-type. I tested it with using the jdbc-type="LONGVARCHAR". Then jpox uses ntext column types for those fields.
> Unfortunatly, there is no way to define this parameter within modello.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira