go to post Chris Sprague · Jan 25, 2018 Ok I think I can confirm this is a bug in Intersystems's query provider for Entity Framework.The order clause is being generated at the same level as the where containing the %VID. Instead, the ORDER BY should be moved inward to a query lower, along with the TOP ALL which it requires. I have an example of the broken and fixed queries below.How can I submit this as a bug fix? I can't find a project page or anything, is it internal, or on GitHub?-- This is the InterSystems query (with identifying values and some excess removed for clarity, but structurally intact):SELECT TOP (10) *FROM ( SELECT TOP ALL * FROM ( SELECT * FROM ( SELECT * FROM --Some view or table or sub query AS "Extent1" WHERE -- redacted client specific fields ) AS "Project1" ) AS "Project1" WHERE %VID > 1 ORDER BY "Project1". -- Some Sortable Field DESC) AS "top" -- This is the correct structure for the query (or something similar, the generator may add extra embedded queries...SELECT TOP (10) *FROM ( SELECT * FROM ( SELECT TOP ALL * FROM ( SELECT * FROM --Some view or table or sub query AS "Extent1" WHERE -- redacted client specific fields ) AS "Project1" ORDER BY "Project1". -- Some Sortable Field ) AS "Project1" WHERE %VID > 1 DESC) AS "top"
go to post Chris Sprague · Jul 6, 2017 From existing libraries, I think the answer is to script the human-readable telnet connection...https://github.com/agsh/boobst/blob/master/boobst.jsThis guy's written an interesting one in ECMAScript.