[
https://issues.apache.org/jira/browse/OFBIZ-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623783#action_12623783
]
jacques.le.roux edited comment on OFBIZ-1923 at 8/19/08 1:35 PM:
-----------------------------------------------------------------
Afterthought : I think I was thinking that the relationship comes from Party to
its geo location history. But I really don't know why I used a *one*
relationship from Party to its geo location history. This makes no sense at
all... I guess I did copy the lines from somewhere but did not think much about
their contents...
Thanks for your clear explanation ! I forgot that the entity engine is able to
automatically create the reverse many relationship. It"s easier to do it in
this direction...
was (Author: jacques.le.roux):
Afterthought : I really don't know why I used a one relationship from Party
to its geo location history. This makes no sense at all... I guess I did copy
the lines from somewhere but did not think much about their contents...
Thanks for your clear explanation !
> 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, 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.
