I encountered this bug when using EF.Functions.DateDiffSecond in a nested query. DATEDIFF(second, [w1].[StartedAt], [w1].[CompletedAt]) to work properly. It also generates an invalid second AS [c1] in ...
An Azure Functions QuickStart project that demonstrates how to use both SQL Triggers and SQL Output Bindings with the Azure Developer CLI (azd) for rapid, event-driven integration with Azure SQL ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results
Feedback