ORA-01745: invalid host/bind variable name when using the same variable multiple times in EF7 query Where()

ORA-01745: invalid host/bind variable name when using the same variable multiple times in EF7 query Where()

Hi, 

were are currenly using Devart.Data.Oracle.EFCore v10.1.134.7 in combination with EF7 on net6.0. Whenever we use a query that uses the same variable 2 times or more in a Where() method we get an ORA-01745 exception.

Example:
  1.             var today = DateTime.Today;
  2.             var someEntity = await _dbContext.SomeEntities
  3.                 .Where(p => p.Startdate <= today && p.Enddate >= today)
  4.                 .FirstOrDefaultAsync(cancellationToken);
gives following exception:

Devart.Data.Oracle.OracleException: 'ORA-01745: invalid host/bind variable name':
This exception was originally thrown at this call stack:
    Devart.Data.Oracle.dq.a(Devart.Data.Oracle.ay, int)
    Devart.Data.Oracle.dq.a(int, Devart.Data.Oracle.bx)
    Devart.Data.Oracle.OracleCommand.InternalExecute(System.Data.CommandBehavior, System.IDisposable, int, int, bool)
    Devart.Common.DbCommandBase.ExecuteDbDataReader(System.Data.CommandBehavior, bool)
    Devart.Data.Oracle.Entity.ao.bz(System.Data.CommandBehavior)
    Devart.Common.Entity.cs.ExecuteDbDataReader(System.Data.CommandBehavior)
    Devart.Data.Oracle.Entity.ao.ExecuteDbDataReader(System.Data.CommandBehavior)
    System.Data.Common.DbCommand.ExecuteDbDataReaderAsync(System.Data.CommandBehavior, System.Threading.CancellationToken)

The dbMonitor outputs following WHERE clause:
WHERE "b".STARTDATE<= :p__today_0 AND "b".ENDDATE>= ::p__today_0

As one can see: the second p__today_0 starts with a double :: which is probably the cause?

Currently, our workaround is to use multiple variables containing the same value:
  1.    var today = DateTime.Today;
  2.    var alsoToday = DateTime.Today;
  3.             var someEntity = await _dbContext.SomeEntities
  4.                 .Where(p => p.Startdate <= today && p.Enddate >= alsoToday)
  5.                 .FirstOrDefaultAsync(cancellationToken);
Is it possible to fix this issue?