[
https://issues.apache.org/jira/browse/OFBIZ-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623562#action_12623562
]
Jacques Le Roux commented on OFBIZ-1923:
----------------------------------------
Thank for your comment David,
1 and 2 done in new patch, I also moved above (in its block) the entity
AgreementEmploymentAppl.
For 3, I get warns about joint entities FixedAssetGeoPoint and
PartyAssetGeoPoint and field missing in related entities, like <<The number of
primary keys (3) of related entity PartyGeoPoint does not match the number of
keymaps (1) for relation of type one "PartyGeoPoint" of entity Party.>>. I
foresaw that but I did not know how to deal with since adding the required
fields (geoPointId and fromDate) to Party and FixedAsset sounds weird to me.
Maybe we could remove the geoPointId from keymaps in joint entities, since
fromDate should be sufficient, and then add only the fromDate field in Party
and Fixedasset, maybe with a thruDate field too then ?
> 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.
