[
http://jira.codehaus.org/browse/MRM-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181594#action_181594
]
Marc Lustig commented on MRM-1198:
----------------------------------
We tried fxing this by changing the JDO-schema for Oracle:
For all fields "url" as well as "issueManagementUrl" and "connection" we
changed as follows
<field name="url">
<column length="2500" jdbc-type="VARCHAR2"/>
</field>
As a result we got the following error on startup:
[ContainerBackgroundProcessor[StandardEngine[Catalina]]] ERROR JPOX.MetaData
- The following error occurred while parsing <column> nested within
<field name="url"
null-value="none">
</field>
Reverting the fields which are primary keys back to the original configuration
did not help. Same error.
Only reverting ALL fields back to the original state caused the webapp to
startup again.
IMO, it should be possible to change the jdbc-type to any db-specific
character-field without compaints from the JDO-impl.
Furthermore, for certain fields, this is not only of "cosmetic" value, it is a
functional necessity, as the URL's often surpass 250 chars.
> field length for ARCHIVA_SCM.URL is too short
> ---------------------------------------------
>
> Key: MRM-1198
> URL: http://jira.codehaus.org/browse/MRM-1198
> Project: Archiva
> Issue Type: Bug
> Components: repository scanning
> Affects Versions: 1.2.1
> Environment: Oracle RAC
> Reporter: Marc Lustig
> Fix For: 1.2.2
>
>
> java.sql.SQLException: ORA-12899: value too large for column
> "CONTINUUM_12"."ARCHIVA_SCM"."URL" (actual: 267, maximum: 250)
> I propose to change the field length to 1020.
--
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
