It seems you can still use NHibernate by setting session factory setting *hbm2ddl.keywords* to "none" (disabling keywords import)
You can read more about this setting and all implications here Auto Quote Table/Column names - NHibernate <https://nhibernate.info/blog/2009/06/23/auto-quote-table-column-names.html> On Friday, November 26, 2021 at 12:03:51 AM UTC+2 [email protected] wrote: > Some people on our team are attempting the same thing - and running into > the same issue. > The trouble is with underlying SQLClient that's issuing query using clr > dependent function ASSEMBLYPROPERTY which is not supported in SQL Edge. > > > https://github.com/dotnet/SqlClient/blob/main/src/Microsoft.Data.SqlClient/src/Microsoft/Data/SqlClient/SqlMetadataFactory.cs > It seems like there would be a technically equivalent way to perform this > query without the function. > Would be nice if the provider library was able to operate in an ANSI sql > compatible manner if desired. > > This issue is related to this gentlemen's post as well. > https://github.com/nhibernate/nhibernate-core/issues/2087 > > > On Monday, November 22, 2021 at 9:55:23 AM UTC-5 [email protected] > wrote: > >> Hello, >> >> When we try to use Azure SQL Edge instead of MSSQL Server with NHibernate >> we always get: >> >> SqlException: Common Language Runtime(CLR) is not enabled on this >> instance. >> >> Why does NHibernate need CLR support and how to disable it? Azure SQL >> Edge does not support CLR and never will. >> >> We just don't see why NHibernate would need it as it supports so many >> different databases and CRL is a very minor feature for SQL Server. >> >> Any ideas? >> > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nhusers/de5c494c-4e10-4b4b-93d0-e4ed24c5eee7n%40googlegroups.com.
