You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Azure Functions SQL Extension or Extension Bundle Version:
3.1.169-preview, but looking at code in github appears to be an issue with latest
Is this a deployed or local function:
deployed to azure function app
What type of Database are you using? (Run SELECT @@VERSION as Version, SERVERPROPERTY('EngineEdition') as EngineEdition on your database)
Microsoft SQL Azure (RTM) - 12.0.2000.8 Oct 2 2024 11:51:41 Copyright (C) 2022 Microsoft Corporation 5
List any custom settings for your function app. This could be a custom time-out defined specifically for your database server or optional configuration that can be customized for the app defined here.
Steps to Reproduce:
create table with columns in uppercase
access table with class properties in lowercase
Our app was previously .net6, using a very old SQL extension (0.1.483-preview). When we upgraded the app to .net8, we also upgraded the sql extension to 3.1.169-preview. Since then, we run into the error generated from GetExtraProperties
Default collation is SQL_Latin1_General_CP1_CI_AS, which is case insensitive, so mismatch case on column names should not be an issue.
The text was updated successfully, but these errors were encountered:
3.1.169-preview, but looking at code in github appears to be an issue with latest
deployed to azure function app
SELECT @@VERSION as Version, SERVERPROPERTY('EngineEdition') as EngineEdition
on your database)Microsoft SQL Azure (RTM) - 12.0.2000.8 Oct 2 2024 11:51:41 Copyright (C) 2022 Microsoft Corporation 5
Steps to Reproduce:
Our app was previously .net6, using a very old SQL extension (0.1.483-preview). When we upgraded the app to .net8, we also upgraded the sql extension to 3.1.169-preview. Since then, we run into the error generated from GetExtraProperties
Default collation is SQL_Latin1_General_CP1_CI_AS, which is case insensitive, so mismatch case on column names should not be an issue.
The text was updated successfully, but these errors were encountered: