Login
Log in using an SSO provider:
Fedora Account System
Red Hat Associate
Login using a Red Hat Bugzilla account
Forgot Password
Create an Account
Red Hat Bugzilla – Bug 1440765
Home
New
Search
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh94 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
[?]
This site requires JavaScript to be enabled to function correctly, please enable it.
Bug 1440765
-
Wrong OData results with multiple self relationships
Summary:
Wrong OData results with multiple self relationships
Keywords
:
Status
:
CLOSED CURRENTRELEASE
Alias:
None
Product:
JBoss Data Virtualization 6
Classification:
JBoss
Component:
Teiid
Sub Component:
---
Version:
6.3.0
Hardware:
Unspecified
OS:
Unspecified
Priority:
unspecified
Severity:
urgent
Target Milestone:
DR4
Target Release
:
6.4.0
Assignee:
Van Halbert
QA Contact:
Jan Stastny
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+
depends on
/
blocked
Reported:
2017-04-10 12:40 UTC by
Van Halbert
Modified:
2018-02-13 17:36 UTC (
History
)
CC List:
9 users
(
show
)
aszczucz
blafond
dlesage
drieden
gjospin
jolee
jschatte
thauser
vhalbert
Fixed In Version:
Doc Type:
If docs needed, set a value
Doc Text:
If an OData entity had multiple self-relationships, only the first foreign key was used no matter which navigation was queried. As a consequence, the wrong data was returend to the user. This has now been fixed. Users can have multiple self-relationships in queries and the correct data is returned.
Clone Of:
Environment:
Last Closed:
2018-02-13 17:36:51 UTC
Type:
Bug
Embargoed:
Attachments
(Terms of Use)
Links
System
ID
Private
Priority
Status
Summary
Last Updated
Red Hat Issue Tracker
TEIID-4852
0
Blocker
Resolved
Wrong OData results with multiple self relationships
2018-02-07 23:35:56 UTC
Comment 2
David Le Sage
2017-11-23 04:06:56 UTC
Documented as a resolved issue in the release notes.
Note
You need to
log in
before you can comment on or make changes to this bug.