I would add more optional parameters as mentioned here:
- number of rows per round trip
- which columns to return
- set a maximum number of rows to return
- whether to include the content of the simple object columns
The last one is very important because I noticed that rows containing large amount of data in simple object columns slow down the whole query even if I don’t use the content of the simple object column.
But, when those rows are sent to the client, the content of the simple object is not sent, and another roundtrip will be required if the client needs them.
So, if my feelings are correct (I didn’t make any serious testing here), simple object columns are never lazy in the server and always lazy in the client. This means that we have the worst of both worlds: in the server it’s slow even if you don’t need simple object data, in the client it’s slow when you do need it, because it’s always lazy.