-
Notifications
You must be signed in to change notification settings - Fork 928
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
NH-3918 - Nominate equality expressions in SELECT clauses #522
Conversation
…nts in them * Allow for entity equality to be correctly translated to HQL * Prevents unneeded joins and caching of entities in the query plan
Rebased on master |
Can this be included in 4.1.0? |
I prefer to proceed with 4.1 as is rather than risk further delays by going into reviewing something. There is always going to be "one more PR". Better we try to get back to more frequent releases. |
var bob = session.Query<Owner>().Single(o => o.Name == "Bob"); | ||
|
||
var queryWithWhere = session.Query<Entity>() | ||
.Where(WhereExpression(bob)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note for future - this indenting looks wrong depending on tab-size, because tab has been used also for alignment within a statement. Tabs are for indenting, space for alignment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noted. NH differs from my usual development that uses spaces for everything, so I'm used to just pressing tab to align things.
with constants in them