Possibly wrong SQL with ExpressionPredicate

First I must say that the final result is working as expected. But when I tried to see generated SQL through SQL Server Profiler I think that it have unnecessary NOT Boolean expression.

This is my ExpressionPredicate public static Expression<Func<Employee, Department, bool>> DepartmentPredicate => ( e, d ) => e.DepartmentId == d.DepartmentId && !d.Deleted;

And this is generated SQL

SELECT
*
FROM
    [Common].[Employee] [t4]
    LEFT JOIN [Common].[Department] [t1] ON [t4].[DepartmentId] = [t1].[DepartmentId] AND NOT (1 = [t1].[Deleted])

Notice NOT (1 = [t1].[Deleted]). I think this should be 0 = [t1].[Deleted].

Any thoughts on this?

Environment details

linq2db version: 1.9.0
Database Server: SQL Server
Framework version: .NET Framework 4.6.1

[sdanyliv]

I think we can do something in that area in V2. For bit fields it should work.

[MaceWindu]

Another voice to use 0 as baseline. Working on Access ODBC driver support I’ve discovered that it is not always 1 or 0… it could be -1 and 0