Hi,
new version of dotConnect is not working with generic OrderBy (my previous post). It's also not working with any construction like
.OrderBy(e => e.Property) with any property given.
It was working in version 9.5.520, now all queries are constructed with unnecessary nesting and not declared "c"
SELECT "t".*
FROM (
SELECT "t0".*
FROM (
SELECT (...), "e"."X" AS "X0", "e"."X" AS "X00"
FROM "A" "e"
INNER (...)
WHERE (...)
ORDER BY "c"
OFFSET :p__p_0 ROWS
) "t0"
ORDER BY "t0"."X"
OFFSET :p__p_0 ROWS
) "t"
ORDER BY "t"."X"
OFFSET :p__p_0 ROWS FETCH NEXT :p__p_1 ROWS ONLY
Devart.Data.Oracle.OracleException (0x80004005): ORA-00904: "c": invalid identifier
at ? . ?()
at ? ()
at ? . ?()
at ? . ?()
at ? .(? , Int32 )
at ? .? ?(Int32 , )
at Devart.Data.Oracle.OracleCommand.InternalExecute(CommandBehavior behavior, IDisposable disposable, Int32 startRecord, Int32 maxRecords, Boolean nonQuery)
at Devart.Common.DbCommandBase.ExecuteDbDataReader(CommandBehavior behavior, Boolean nonQuery)
at . ?? ?? ? ?? ? ? ?? ?(CommandBehavior )
at .ExecuteDbDataReader(CommandBehavior )
at .ExecuteDbDataReader(CommandBehavior )
at System.Data.Common.DbCommand.ExecuteDbDataReaderAsync(CommandBehavior behavior, CancellationToken cancellationToken)
Version of dotConnect you have released is now blocking us from migration to EF Core 2.1.
OrderBy(e => e.Property) broken in version 9.6.540
Re: OrderBy(e => e.Property) broken in version 9.6.540
Thank you for your report. We have reproduced the bug and are working on it. We will provide the fix as soon as possible.
Re: OrderBy(e => e.Property) broken in version 9.6.540
The bug with paging in EF Core 2.1 is fixed. The internal build with the fix: https://www.devart.com/pub/nuget_oracle_9_6_554.zip.
Re: OrderBy(e => e.Property) broken in version 9.6.540
New build of dotConnect for Oracle 9.6.558 is available for download: viewtopic.php?f=1&t=37474.