Smit Patel

@maumar - Is this already done?

@davisnw - A work-around posted in Feb 2017 can easily get outdated with newer version of EF as underlying APIs can change.

@nikkhoo63 - This seems like a product issue. Can you provide repro solution/steps?

@dylinmaust - It does not require additional column. The point is you create a shadow property in your complex type and configure it using `HasColumnName` to use the same column...

Can you make following change and see if it works for you? ```C# modelBuilder .Property(p => p.Name) .HasColumnName("Name") //

Design Notes: - Since query/table hints are a lot provider specific, there is no good relational level API (yet). Enums for options will have issue with provider specific code in...

cc: @ralmsdeveloper

@ralmsdeveloper - That is what we decided explicitly not to do it. Unless there is any common query hint across all providers. Especially we cannot use any method with string...

@roji - The current plan is to flow QueryAnnotations to SelectExpression. While it is obvious that query hints (SelectExpression level annotations) are covered by that, you can still use the...

- It indeed difficult to design an API for such cases. Table hints is also one such case. What if the user wants to apply `No Lock` on 1 table...