You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Michael Bouschen (Jira)" <ji...@apache.org> on 2022/02/17 19:58:00 UTC

[jira] [Updated] (JDO-756) Enhance PK to avoid LongIdentity/StringIdentity dependencies

     [ https://issues.apache.org/jira/browse/JDO-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Bouschen updated JDO-756:
---------------------------------
    Component/s: api

> Enhance PK to avoid LongIdentity/StringIdentity dependencies
> ------------------------------------------------------------
>
>                 Key: JDO-756
>                 URL: https://issues.apache.org/jira/browse/JDO-756
>             Project: JDO
>          Issue Type: Improvement
>          Components: api
>            Reporter: joseaio
>            Priority: Major
>
> Please see: JDO Guides : M-N Attributed Relation
> http://www.datanucleus.org/products/accessplatform_3_1/guides/jdo/many_many_attributed/index.html
> public class BusinessRelation{
> · private Customer customer; // PK
> · private Supplier supplier; // PK
> BusinessRelation.PK requires:
> · public LongIdentity customer; // LongIdentity dependency
> · public LongIdentity supplier; // LongIdentity dependency
> In Customer and Supplier classes: the id is long (not LongIdentity)
> · private long id; // PK
>  
> I think more convenient enhance BusinessRelation.PK to allow long types (and remove LongIdentity/***Identity dependencies):
> BusinessRelation.PK
> · public long customer;   // Use long as Customer.id field
> · public long supplier; // Use long as Supplier.id field
> note: the same rule for other basic types (String, Dates, Integer, Long, Byte...)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)