[teiid-issues] [JBoss JIRA] (TEIID-4105) ODATA: Duplicate NavigationProperty name
Ramesh Reddy (JIRA)
issues at jboss.org
Tue Mar 29 19:33:00 EDT 2016
[ https://issues.jboss.org/browse/TEIID-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183585#comment-13183585 ]
Ramesh Reddy commented on TEIID-4105:
-------------------------------------
I agree that the name of the table used for the navigation name, but the having multiple relations between *same* two tables seems like strange requirement.
> ODATA: Duplicate NavigationProperty name
> ----------------------------------------
>
> Key: TEIID-4105
> URL: https://issues.jboss.org/browse/TEIID-4105
> Project: Teiid
> Issue Type: Bug
> Components: OData
> Affects Versions: 8.3
> Reporter: Ivan Lucas Vargas
> Assignee: Ramesh Reddy
> Labels: Beta3
> Fix For: 9.0, 8.12.5
>
>
> Entity 1: TransferRule
> Entity 2: FinancialAccount
> TransferRule
> - sourceAccount : FinancialAccount
> - destination : FinancialAccount
> - other attributes
> the mapping to this for odata resolves to
> <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_destinationfinancial_account_id_fk" FromRole="transferrule" ToRole="financialaccount" />
> <NavigationProperty Name="financialaccount" Relationship="LivingODS.transferrule_sourcefinancial_account_id_fk" FromRole="transferrule"
> ToRole="financialaccount" />
> The navigation property name is duplicated with in transfer rule entity.
> Hence some of the Odata client see it as ambiguous element
> Is there a way to customise the Name to
> Name="src_financialaccount" and
> Name="dest_financialaccount"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the teiid-issues
mailing list