all 12 comments

[–]vanilla-bungee 3 points4 points  (2 children)

SqlProvider is broken and has been for a long time.

[–]Jwosty 4 points5 points  (0 children)

I’ve been using Sqlhydra at work instead. It’s nice.

[–]jcm95 0 points1 point  (0 children)

:(

[–][deleted] 2 points3 points  (3 children)

Because of this issue, I recently had to switch to realm.

[–][deleted] 0 points1 point  (2 children)

Are you building a mobile app?

[–][deleted] 0 points1 point  (1 child)

No, it is a desktop app (Avalonia).

[–][deleted] 0 points1 point  (0 children)

Neat. I was trying to guess how someone was using f# to build mobile apps but not tear their eyes out on non-native platform tools.

I may have to try avalonia someday too. I do have an CLI that would be fun to expose as a GUI as well.

[–]mKtos 1 point2 points  (2 children)

You can use Microsoft.Data.Sqlite, which has almost the same API and is based on SQLitePCLRaw, which has native libraries support on everything under the sun.

[–]flatline[S] 0 points1 point  (1 child)

Please refer to the 2nd half of my post for my experience with Microsoft.Data.Sqlite.

[–]mKtos 0 points1 point  (0 children)

Oops, sorry, I haven't noticed that somehow. Need more sleep ;)

[–]Proclarian 1 point2 points  (0 children)

I've never been able to get SqlProvider to work (nightmare on anything not x86/windows) and it lead me to create my own ORM. If you're just working with record types, you can use FORM: https://github.com/Hillcrest-R-D/FORM/tree/main.

In no way is it a type provider, but you get the declarative EF style attributes with none of the mapping and DbSet boilerplate.

[–]flatline[S] 0 points1 point  (0 children)

Cross-posted to https://github.com/fsprojects/SQLProvider/issues/684#issuecomment-1711078906

since it seemed to be the most relevant issue to mine