You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Ate Douma (JIRA)" <je...@portals.apache.org> on 2007/03/09 01:56:24 UTC
[jira] Commented: (JS2-658) COM.ibm.db2.jdbc.DB2Exception:
[IBM][CLI Driver][DB2/NT] SQL0107N The name "FK_PA_METADATA_FIELD_1" is
too long. The maximum length is "18". SQLSTATE=42622
[ https://issues.apache.org/jira/browse/JS2-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479468 ]
Ate Douma commented on JS2-658:
-------------------------------
Wow, 18 characters max. for a foreign key name? That is absurd :)
Well, we can look into reducing the length of all our foreign key names some time.
Note: fixing a bug cannot be done against the same (release) version it was detected in, so I'm gonna bump the Fix Version up to 2.2-dev
> COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2/NT] SQL0107N The name "FK_PA_METADATA_FIELD_1" is too long. The maximum length is "18". SQLSTATE=42622
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JS2-658
> URL: https://issues.apache.org/jira/browse/JS2-658
> Project: Jetspeed 2
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: Database -- DB2. JDK 1.5_06. Maven 1.0.2
> Reporter: Mahesh Mohan
> Fix For: 2.2-dev
>
>
> When I try to generate and populate my DB2 Database for Jetspeed using Jetspeed-Maven Plugin I am getting the above exception. To fix this temporarly what I went along with was to identify the foreign keys with a name longer then 18 chars and make them shorter. This is a bit of manual step, but works fine with all the databases. So basically we need to get into the jetspeed plugin inside maven_repo (<maven installation dir>\maven_repo\cache\maven-jetspeed2-plugin-2.1-dev\plugin-resources\schema) and manually edit the schema xml's to overcome the above limitation.
> Now, what I would like to know here is, whether this is a known issue or there is something wrong with my configurations moreover is there a better fix for this issue. And if this is a known issue, which release of Jetspeed-maven Plugin will have a solution for the same.
> Any help on this regard will be greatly appreciated.
> Regards
> Mahesh
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org