db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bouschen (JIRA)" <j...@apache.org>
Subject [jira] Closed: (JDO-111) Types of key/value columns and index columns in join tables
Date Sat, 22 Apr 2006 20:01:07 GMT
     [ http://issues.apache.org/jira/browse/JDO-111?page=all ]
     
Michael Bouschen closed JDO-111:
--------------------------------

    Fix Version: JDO 2 beta
     Resolution: Fixed

> Types of key/value columns and index columns in join tables
> -----------------------------------------------------------
>
>          Key: JDO-111
>          URL: http://issues.apache.org/jira/browse/JDO-111
>      Project: JDO
>         Type: Bug

>   Components: tck20
>     Reporter: Michael Watzek
>     Assignee: Michael Watzek
>      Fix For: JDO 2 beta

>
> PC classes like "HashtableStringValueCollections" have several fields of type "java.util.Map"
where (sometimes) keys are FCOs (e.g. SimpleClass instances) and values are strings. The types
of keys and values differ and can be derived by the classname.
> Each of these fields is mapped to a separate (join) table having join columns, key columns,
value columns, and index columns. In the current schema, all of these columns have type "INTEGER".
This is a bug.
> Keys and values of type "java.lang.String" must be mapped to columns of type "VARCHAR".
Furthermore, join tables which are mapped by fields of maps or sets do not have index columns.
However, we should keep index columns for TreeSets and TreeMaps.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message