[
https://issues.apache.org/jira/browse/JDO-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
joseaio updated JDO-756:
------------------------
Description:
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...)
was:
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; // Use same name as BusinessRelation field
public LongIdentity supplier; // Use same name as BusinessRelation field
Instead in Customer and Suplier classes: the id is long (not LongIdentity)
private long id; // PK
I think more convenient enhance BusinessRelation.PK to allow long types (and
remove Long/StringIdentity dependencies):
public long customer; // Use same name as BusinessRelation field
public long supplier; // Use same name as BusinessRelation field
note: the same for any other basic types (String, Dates,... included)
> Enhance PK to avoid LongIdentity/StringIdentity dependencies
> ------------------------------------------------------------
>
> Key: JDO-756
> URL: https://issues.apache.org/jira/browse/JDO-756
> Project: JDO
> Issue Type: Improvement
> Reporter: joseaio
> Fix For: JDO 3.2
>
>
> 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
(v6.3.4#6332)
