This question is locked. New answers and comments are not allowed.
I submitted a ticket asking about this, but didn't hear back. So I was hoping maybe someone on the forums could answer.
Watching the generated SQL generated by OpenAccess it appears that prior to filitering, OpenAccess selects every row from a table.
For example, I see queries like this:
SELECT a.[Code] AS COL?, a.[AmountBilledNow] AS COL?, a.[FooterText] AS COL?, a.[FullOrderAmount] AS COL?, a.[LoginPrefix] AS COL?, a.[NeedsLogin] AS COL?, a.[NeedsPIN] AS COL?, a.[SKUCode] AS COL?, a.[SalesFlowKey] AS COL?, a.[ShortSummary] AS COL?, a.[TermsURL] AS COL?, a.[ThemeId] AS COL?, a.[Title] AS COL? FROM [usp_OrderCode] a ORDER BY a.[Code]
Generated when I have a statement like this:
When I turn the debug level to "all" I can verify that it has definitely selected all rows from the table.
Is this normal behavior?
Thanks
Watching the generated SQL generated by OpenAccess it appears that prior to filitering, OpenAccess selects every row from a table.
For example, I see queries like this:
SELECT a.
Generated when I have a statement like this:
dbContext.OrderCodes.Where(oc => oc.Code == "test_order_code")
When I turn the debug level to "all" I can verify that it has definitely selected all rows from the table.
Is this normal behavior?
Thanks