Yes, I am not sure why I did not choose named parameters, that was wrong.

I can not say I understand negate one fully.

OData procedure issues ---------------------- Key: TEIID-2660 URL: https://issues.jboss.org/browse/TEIID-2660 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.3 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 8.5 Calling a procedure through Teiid's odata interface has several issues. First is that joda time values are passed directly - which the runtime will not be able to convert to analogous Teiid time types. Ultimately this appears as a classcastexception, which is due to logic in the joda time AbstractPartial.compareTo method (which may be reported with an erroneous message and seems odd in general, but is their way of saying the comparison is invalid). Another is that the logic assumes that the url will be called with the positional ordering of the parameters preserved. We should use named parameters instead.