[
https://issues.apache.org/jira/browse/OFBIZ-4349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erwan de FERRIERES updated OFBIZ-4349:
--------------------------------------
Attachment: OFBIZ-4349.patch
The previous commit was to correct the problem occuring when realEntity
pkFieldName is different from viewEntity pkColName, but it's only working with
simple view and it breaks retrieving i18n for view with multiple entity and
pkColName == pkFieldName.
So this new patch solves the two situations. Now the method :
use pkField of realEntity
and retrieve for each pkField the correct colAlias
I'm waiting for your comments.
Cheers,
> commit r1077940 breaks the function to retrieve i18n translation from real
> entity underlying a view
> ---------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-4349
> URL: https://issues.apache.org/jira/browse/OFBIZ-4349
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Leon
> Attachments: OFBIZ-4349.patch
>
>
> in r1077940 changeset
> ([https://fisheye6.atlassian.com/changelog/ofbiz?cs=1077940]), it gets the pk
> fiels from view entity instead of previous real entity. I cannot understand
> what author erwan commented: "When using a view and fields with different
> names than in the original entity, the model was taking the original names so
> this could lead to warnings". The consequence of this commit is it cannot
> retrieve i18n translation from real entity now because the pks of view entity
> is usually different than that of its base tables.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
