algo-web/odatametadata

ODataMetadata

This separates out the underlying object structure of the OData metadata generated by the Algo-Web/POData package, along with the .yml template files that are fed to JMS serializer.

odatametadata's Issues

Move phpunit 5.6 from require to require-dev

For purpose of non problematic install of POData that is using ODataMetadata as dedepency, for those who use phpunit in version 5.7 and above, please reconsider moving "phpunit/phpunit": "^5.6" from require to require-dev, as unnecessary dependency in non dev mode.

Drop out dep on JMS serialiser

@c-harris , can you fill this in a bit more?

Multiplicities are swapped

When adding a non-many-to-many relation, principal multiplicity seems to end up on the dependent end of things, and vice versa.

This seems to happen somewhere in MetadataManager, inside addNavigationPropertyToEntityType method.

Manually reversing order of calls in the call to createAssocationFromNavigationProperty in testbed application looks to correct this - supplied multiplicities end up in their correct location

What exactly is TTextType supposed to do?

I get the impression that it's supposed to carry some sort of text payload, from how it's used in the codebase. But how does it do that? Where is said payload stashed?

Lacking Readme

We really should put together a basic Read me at some point one paragraph should do.

TEntityTypeType.isOK letting stuff through

Cf Odata v3 spec:

6 Entity Type Constructs
Entity types are nominal structural types with a key that consists of one or more references to structural properties. An entity type by definition has an independent existence and can be created, updated or deleted independently of any other types. An entity type is the template for an entity: any uniquely identifiable record such as a customer or order.

A key MUST be supplied if and only if the entity type does not specify a base type. The key consists of one or more references to structural properties of the entity type.

Check legitimate/appropriate field default values

When has a property has a default value assigned, that class's isOK method should verify the string value is appropriate for that type

Excel 2016 connect fails: InvalidVersionNumber: The EDMX version specified in the Version attribute does not match the version corresponding to the namespace of the Edmx element

Hi,

I'm trying to use this project and algo-web/podata to deliver data from MySQL to Excel 2016. I have managed to set up a Sample data set on my local dev machine as follows:

http://dss.example.com/proto/odata.svc/ delivers a simple XML document:

<service xml:base="http://dss.example.com/proto/odata.svc/"><workspace><atom:title>Default</atom:title><collection href="Samples"><atom:title>Samples</atom:title></collection></workspace></service>

http://dss.example.com/proto/odata.svc/Samples in Chrome delivers my data as xml

http://dss.example.com/proto/odata.svc/Samples?$format=json in Chrome delivers my data as json, if I make a small tweak in JsonLightOdataWriter (I may create a separate issue)

I've collected the headers sent by Excel and replicated them in this curl call:

curl -H "User-Agent: Microsoft.Data.Mashup (https://go.microsoft.com/fwlink/?LinkID=304225)" -H "OData-MaxVersion: 4.0" -H "Accept: application/json;odata.metadata=minimal" -H "Accept-Encoding: gzip, deflate" -H "Host: dss.example.com" http://dss.example.com/proto/odata.svc/Samples

and that delivers my data as JSON as well. However, somehow it doesn't work in Excel.

When I put http://dss.example.com/proto/odata.svc/Samples into Excel as an OData source, I get an error message "No Writer can handle this request". This is the error I have when not making that tweak in JsonLightOdataWriter

Then I checked the odata.org examples and when I put them into Excel, I get the authentication popup. So I tried http://dss.example.com/proto/odata.svc/ in Excel and get the error message as per title. I assume it is related to output from http://dss.example.com/proto/odata.svc/$metadata, which is:

	<edmx:Edmx xmlns:edmx="http://schemas.microsoft.com/ado/2007/06/edmx" xmlns="http://schemas.microsoft.com/ado/2009/11/edm" xmlns:cg="http://schemas.microsoft.com/ado/2006/04/codegeneration" xmlns:annotation="http://schemas.microsoft.com/ado/2009/02/edm/annotation" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata" Version="3.0">
	<edmx:DataServices m:MaxDataServiceVersion="3.0" m:DataServiceVersion="3.0">
	</edmx:DataServices>
	</edmx:Edmx>

But I can't see anything that could be wrong.

Any idea what is missing here? Is there a guide to connect Excel to POData providers built with your project?