Lambda generate wrong query - EF Core

[guiwaltricke]

Hi, we are getting a error using "Devart.Data.PostgreSql.EFCore" and "Devart.Data.Oracle.EFCore"

we have a function that generate a lambda expression using commands, here a example of a lambda generated:

.Lambda #Lambda1<System.Func`2[Useall.Sign.Dominio.Documentos.Documento,System.Boolean]>(Useall.Sign.Dominio.Documentos.Documento $x)
{
$x.Id == 1 & $x.CodigoSistema == .Constant<System.Nullable`1[System.Int32]>(1)
}
Print: https://prnt.sc/t0xgyp

Devart generates this query:

SELECT COUNT(*)
FROM SIGN_DOC AS s
WHERE (s.IDUTILIZADOR = 0) AND ((s.IDDOC = 1) & ((s.IDSISTEMA = 1) AND s.IDSISTEMA IS NOT NULL))

and error appears: "operator does not exist: boolean & boolean"
Print: https://prnt.sc/t0xr7f

This error ocurrs in asp net core, we are using the same code in asp.net tradicional and works very good...

May you guys helpe us?

[guiwaltricke]

Anyone? @Shalex

We really need this working...

Thanks

[Shalex]

The bug with throwing "ORA-00907: missing right parenthesis" with Expression.Or, Expression.And in EF Core 3.1 is fixed in the newest v9.11.1034 build. Please upgrade to v9.11.1034.

If this doesn't help, send us a small test project with the corresponding DDL/DML script for reproducing the issue.

[guiwaltricke]

The bug with throwing "ORA-00907: missing right parenthesis" with Expression.Or, Expression.And in EF Core 3.1 is fixed in the newest v9.11.1034 build. Please upgrade to v9.11.1034.

If this doesn't help, send us a small test project with the corresponding DDL/DML script for reproducing the issue.

Hi @Shalex, the problem is not the "ORA-00907: missing right parenthesis"... the problem is the "&" in the query instead of "and'.

you send us a link for Oracle, but we are working here with Postgres.

Thanks

[Shalex]

Sorry for the misleading message.

If the upgrade to dotConnect for PostgreSQL v7.17.1666 doesn't help, send us a small test project with the corresponding DDL/DML script for reproducing the issue.

[guiwaltricke]

Sorry for the misleading message.

If the upgrade to dotConnect for PostgreSQL v7.17.1666 doesn't help, send us a small test project with the corresponding DDL/DML script for reproducing the issue.

@Shalex, we send an email with a project to simulate, now we are waiting for you..

Thanks.