OData function parameters should not implicitly convert ------------------------------------------------------- Key: TEIID-3910 URL: https://issues.jboss.org/browse/TEIID-3910 Project: Teiid Issue Type: Bug Components: OData Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.13, 8.12.5 OData function param literal strings can be parsed as the expected type with the current code, however this is not the general expectation of odata. It's explicitly mentioned that there is no implicit conversion between string and numeric types: http://docs.oasis-open.org/odata/odata/v4.0/csprd01/part2-url-conventions... And the sample service behaves the same way for DateTimeOffset: http://services.odata.org/V4/Northwind/Northwind.svc/Orders?$filter=Order...