[teiid-issues] [JBoss JIRA] (TEIID-3538) Make OData V2 compatible with LINQPad

[Ramesh Reddy (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-3538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100353#comment-13100353 ] 

Ramesh Reddy commented on TEIID-3538:
-------------------------------------

[~jstastny] It looks like there are couple limitations with LINQPad

1) LINQPad does not seem to handle FunctionImports, i.e Procedures. If the model contains only procedures, no tables then also it acts error.
2) LINQPad does not work with multiple schema, EntityContainers in the $metadata, I mean it will not show all the schemas, it will only show the default. Since in the Teiid VDB's $metadata we will not set any default schema, it finds the first one and uses it. OData V2 does allow multiple Schemas and multiple EntityContainer's in a single $metadata (v4 changed to multiple schema, but single EntityContainer to solve this issue)

We can mark a certain model as it is the default EntityContainer based on some metadata, but that does not exist today. So, right now  my guess is LINQPad is not designed completely for V2 spec.

> Make OData V2 compatible with LINQPad
> -------------------------------------
>
>                 Key: TEIID-3538
>                 URL: https://issues.jboss.org/browse/TEIID-3538
>             Project: Teiid
>          Issue Type: Bug
>          Components: OData
>            Reporter: Ramesh Reddy
>            Assignee: Ramesh Reddy
>              Labels: Final
>             Fix For: 8.7.1.6_2, 8.11
>
>         Attachments: $metadata
>
>
> Current OData V2 implementation is not able to load in LINQPad https://www.linqpad.net/
> Couple issues found
> - List(Edm.xxx) based collections are not supported. V2 Spec did not specify any List based collections. Only Collection(Edm.xxx) type. So, part of TEIID-3471 need to be rolled back and fix with Collection(Edm.xxx) type
> - Explicit definition of "not null" in Entity's key property.
> - TEIID-3471 did not go far enough to define accepts header to have "application/xml", "application/atom+xml" and "application/json" without "chaset=utf-8" appended to it. TEIID-3471 only added $metadata and service document. BTW, I was under the impression that I did add all the required places, and was surprised not see in commit :(



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)