-
Notifications
You must be signed in to change notification settings - Fork 95
Can't parse $metadata #27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Yeah, it could be it. I have just pushed the commit ed1ae8a which fixes parsing of Schema Namespaces. However, I still I need to find a way how to parser Edmx with unexpected XML Namespaces. |
Recognizing that many xml namespaces ae same despite different hosting url we added whitelisted urls for which we granite support. Also we added option to pass custom dict with namespaces in case non of whitelisted is used by your data source. --- Jakub Filak <[email protected]> ---- This commit adds support for XML Namespaces used in #27
My apologies for such a late reply, @pb9k I can see two bugs in
I am also not sure about EnumType - I cannot find any documentation describing this element for OData V2. |
Alright, EnumType is defined in EDMX: https://docs.microsoft.com/en-us/ef/ef6/modeling/designer/advanced/edmx/csdl-spec |
Thanks for taking the time to look at this. I did not understand that this was only for V2 implementations. I believe the data I am working with is based off V4. |
We plan to support V4 - #39 |
The following $metadata does not seem to be able to be parsed by
pyodata
. Any ideas on what makes it problematic? It may be related to #16.The text was updated successfully, but these errors were encountered: