[
https://issues.jboss.org/browse/TEIID-3798?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-3798:
-------------------------------------
In Teiid's case, relationship always terminates in a collection, but the quirky thing
here is the entity does not exist, that is why I was leaning towards the 404. If entity
existed and entity relationship not, then it is empty collection with 200. But in Teiid
case, it hard to differentiate between these two with SQL query generated.
response code for "primary key of parent table not found"
---------------------------------------------------------
Key: TEIID-3798
URL:
https://issues.jboss.org/browse/TEIID-3798
Project: Teiid
Issue Type: Bug
Reporter: Prashanthi Kairuppala
Assignee: Steven Hawkins
Priority: Critical
Hi,
When the primary key of the parent table is not found in the below kind of odata URL:
odata/VDB/ParentTable/123/ChildTable
then the response code is expected to be 404/500 or any error code, but we are getting
200 OK success code.
Thanks,
Prashanthi.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)