[
https://issues.apache.org/jira/browse/OFBIZ-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623762#action_12623762
]
David E. Jones commented on OFBIZ-1923:
---------------------------------------
What is the "AgreementEmploymentAppl" entity doing in there?
As for PartyGeoPoint, it should point to Party but no need for one in the other
direction, the entity engine would automatically add the reverse type "many"
relationship.
It wouldn't really make much sense to try to have a type one relationship going
from Party to PartyGeoPoint, but yes if you wanted to do that you would have to
have fields for the full PK of PartyGeoPoint on the Party entity (but no, we
don't want to do that...).
-David
> Add geolocation to data model.
> ------------------------------
>
> Key: OFBIZ-1923
> URL: https://issues.apache.org/jira/browse/OFBIZ-1923
> Project: OFBiz
> Issue Type: New Feature
> Components: accounting, framework, party, product
> Affects Versions: SVN trunk
> Reporter: Jacques Le Roux
> Assignee: Jacques Le Roux
> Fix For: SVN trunk
>
> Attachments: GeopointDataModel.patch
>
>
> The attached patch is enhancing the current data model following last David's
> suggestion after some exchanges on dev ML. I just added a geoPointId to
> Container.
> I finally used float for latitude, longitude and elevation, instead of
> creating a new degree field type (numeric 18,6).
> Any comments are welcome.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
