Search for existing suggestions

Support ObjectContext.Translate on joined result sets

We sometimes end up doing 20 or more result sets in a single stored proc. Many times, a large majority of these are to bring back a single entry for each navigation property mapping.

I would like to see a "wide" translate function.
If a query has:
SELECT a.*, b.*, c.*, d.*

I'd like to see a version of Translate that can map each row to 4 separate object types, using the assumption that all of object A's columns are first, followed by B's, etc.

This would greatly reduce the size of our stored procs, though there could be a trade off in duplicate objects coming down. Currently, any joins we do server side (which can be 3, 4, sometimes 5 or more levels deep) have to be repeated on each entity we want to return. This leads to a lot of extra code and maintainability issues.

1 vote
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)

We’ll send you updates on this idea

dguisinger shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base