-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GetSchema("DataType") is not compatible with Microsoft Fabric Datawarehouse #2588
Comments
@MaceWindu Looks like both EngineEdition 6 and 11 should be excluded in addition to 9? |
@MaceWindu Thank you for reporting this issue. We will investigate and try to resolve this issue by trying ErikEJ's suggestion to also exclude EngineEdition 6 and 11 in addition to 9 implemented in a fix, PR #2099, for issue #2086. |
@MaceWindu any chance to check a select from sys.assemblies against a engineedition 9 and 11 server? The docs are quite ambigious |
…PROPERTY function fixes dotnet#2588
@arellegue @MaceWindu I have created a PR |
@MaceWindu No worries, I found som docs that states that ASSEMBLYPROPERTY is only supported on "SQL Server" |
I'm glad you have tracked down the issue. Here is the result of select * from sys.assemblies, in case it is helpful.
|
@Hoodah Turned out it was the Assemblypropety function that was causing issues, and my fix adheres to the docs |
Describe the bug
This is basically #2086 but for another SQL Server-like database.
GetSchema('DataType") loads UDT types using CLR features of SQL Server, not supported on
Microsoft Fabric Datawarehouse
leading to exception from server fromaddUDTsToDataTypesTable
method here.To reproduce
Expected behavior
API doesn't try to access unsupported by server functionality.
Further technical details
Microsoft.Data.SqlClient version: 5.2.1
Additional context
Microsoft Fabric Datawarehouse unsupported features page doesn't list CLR support explicitly (or I cannot find it), but I wouldn't expect it to support CLR as effectively obsolete feature.
Original issue : linq2db/linq2db#4536
The text was updated successfully, but these errors were encountered: