]
Steven Hawkins commented on TEIID-5681:
---------------------------------------
Usually the importer will automatically handle widening unsigned types. However the Teiid
importer was not handling bigint - TEIID-5605
So if you are using the Teiid connection importer, that will be automatically addressed
with that change. I'm not sure if the Teiid Designer JDBC importer correctly handles
that situation or as you say if it should be producing a warning.
Error when trying to sort an expanded data set
----------------------------------------------
Key: TEIID-5681
URL:
https://issues.jboss.org/browse/TEIID-5681
Project: Teiid
Issue Type: Bug
Components: OData
Reporter: Christoph John
Assignee: Steven Hawkins
Priority: Major
Hello together,
when using orderby together with an odata expand operation I get and error. The
statement I am trying looks as follows:
https://morpheus.fritz.box/odata4/svc/my_nutri_diary/Diary?$select=idDiar...
The error is:
<error
xmlns="http://docs.oasis-open.org/odata/ns/metadata">
<code>null</code>
<message>
TEIID31202 Detected that an already sorted set of values was not in the expected order
(typically UTF-16 / UCS-2). Please check the translator settings to ensure character
columns used for joining are sorted as expected.
</message>
</error>
Please note, when using orderby without expand, the orderby is working as expected. The
attribute which shall be used for ordering has the following type:
<Property Name="MealNumber" Type="Edm.String"
Nullable="false" MaxLength="1">
In the underlaying database it is defined as an
ENUM('1','2','3','4','5')