-
-
Notifications
You must be signed in to change notification settings - Fork 469
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Select<T>(x => x.ExplicitSql(text)) transform in Select statements #1926
Labels
Milestone
Comments
There seems to be a deep assumption in Marten that raw sql can only be used for Where clauses or full queries only. This needs to be changed (surgery). |
Something like this would be a very useful addition. I currently need to use 'lag' and 'lead' windowing functions and currently it seems my only option is to pass a SQL string verbatim. |
jeremydmiller
added a commit
that referenced
this issue
Dec 21, 2023
Working on this one today Tasks
|
jeremydmiller
added a commit
that referenced
this issue
Dec 21, 2023
Boom! Working locally. |
jeremydmiller
added a commit
that referenced
this issue
Dec 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In some cases it maybe desirable to express a projection to a property that Marten's LINQ provider is unable to parse (yet).
In such case it would be so nice if we could have something like
or maybe
A certain convention will need to be established and documented perhaps for inner subqueries or related document fetches (where the "d" alias would perhaps differ).
The text was updated successfully, but these errors were encountered: