Add parameter of FormattableString as an overload to CreateSQLQuery

Moved here.

It was just an idea I got from seeing how EF Core 2 does it.

See https://channel9.msdn.com/Blogs/dotnet/NET-Core-20-Released (Starts at 1:16:00).

Yes I had seen that. Once escaped they should be treated as previously I think (but not yet ascertain). I have just missed the escaping in my previous comment, using the Markdown's one instead of the Jira's one.

By the way it looks to me there is an unfortunate typo in 17.1.4 example : c.MOTHER_ID = c.ID should be c.MOTHER_ID = m.ID in the first and second example. And all examples do mix c/cat and m/mother aliases, the third example being clearly wrong, the others at least suspicious. (I have not checked if the HQL alias in query should also match the curly alias.)

Yes I had seen that. Once escaped they should be treated as previously I think (but not yet ascertain). I have just missed the escaping in my previous comment, using the Markdown's one instead of the Jira's one.

By the way it looks to me there is an unfortunate typo in 17.1.4 example : c.MOTHER_ID = c.ID should be c.MOTHER_ID = m.ID in the first and second example. And all examples do mix c/cat and m/mother aliases, the third example being clearly wrong, the other at least suspicious. (I have not checked if the HQL alias in query should also match the curly alias.)

Yes I had seen that. Once escaped they should be treated as previously I think (but not yet ascertain). I have just missed the escaping in my previous comment, using the Markdown's one instead of the Jira's one.

By the way it looks to me there is an unfortunate typo in 17.1.4 example : c.MOTHER_ID = c.ID should be c.MOTHER_ID = m.ID in the first and second example. And all examples do mix c/cat and m/mother aliases, the third example being clearly wrong, the other at least suspicious. (I have not checked if the HQL alias in query should also match the curly alias.)