Yes you are right, that is a missing functionality of our OQL parser. The query can be re-written in another way though where the result set will be the one that you desire. Since the Product
has a collection of properties I assume that the property has a reference to a Product
Here is the new look of the query then:
|"SELECT * FROM PropertyExtent AS p ORDER BY p.val"
The query generated will still contain a JOIN between the Product
tables as long as you use the product reference
of the property
objects from the result set.
I hope this is not to confusing, if you need more clarification please send us a sample project or describe the final goal you want to achieve and we can make a sample demonstrating this for you.
the Telerik team