EF Core 6 Arbitrarily Adding ‘WHERE 1 = 0’ Clause
I have moved my production code from an on-premises server to an Azure server. I noticed that most queries are returning 0 results, but when counting the rows, they return the correct count. After investigating using SQL Profiler, I noticed that EF Core is adding a “WHERE 1 = 0” condition to some queries, even though this was not added in the code.
EF Core 6 Arbitrarily Adding ‘WHERE 1 = 0’ Clause
I have moved my production code from an on-premises server to an Azure server. I noticed that most queries are returning 0 results, but when counting the rows, they return the correct count. After investigating using SQL Profiler, I noticed that EF Core is adding a “WHERE 1 = 0” condition to some queries, even though this was not added in the code.
EF Core 6 Arbitrarily Adding ‘WHERE 1 = 0’ Clause
I have moved my production code from an on-premises server to an Azure server. I noticed that most queries are returning 0 results, but when counting the rows, they return the correct count. After investigating using SQL Profiler, I noticed that EF Core is adding a “WHERE 1 = 0” condition to some queries, even though this was not added in the code.
EF Core 6 Arbitrarily Adding ‘WHERE 1 = 0’ Clause
I have moved my production code from an on-premises server to an Azure server. I noticed that most queries are returning 0 results, but when counting the rows, they return the correct count. After investigating using SQL Profiler, I noticed that EF Core is adding a “WHERE 1 = 0” condition to some queries, even though this was not added in the code.