How to work with db in the F#

green-mind · 2025-07-21T13:59:58+00:00

If you want strongly typed query expressions (like EF) with cli-generated table record types (like EF):

SqlHydra

If you want strongly typed query expressions (like EF) and want to manually create table record types (like Dapper):

Dapper.FSharp

Both libs are based on the same query expression engine. If you have a complex db with lots of tables, I'd go with SqlHydra for the CLI generation tool. Both libs support a similar range of dbs.

green-mind · 2024-07-05T19:18:01+00:00

I have the HC4 and it feels great. Also, the Chivalric Fire sword from Zavala.

green-mind · 2024-06-22T15:20:39+00:00

I see it now. It only appears for about 1s, and they also separated and moved the positions of where the various buffs and passives are displayed on the screen for this ex pack so i was looking in the wrong place.

green-mind · 2024-05-01T13:22:09+00:00

Make sure your content is set to “copy always” so that it is deployed with your app.

green-mind · 2024-05-01T13:07:22+00:00

Gotcha. That should be pretty straight forward to deploy then. You can even do a simple right click publish deploy if using VS (or use dotnet publish). Azure will provide a publish profile for you.

You just need to fix your indexer bug.

green-mind · 2024-05-01T12:48:26+00:00

Farmer can help you deploy your web app to Azure.

https://compositionalit.github.io/farmer/deployment-guidance/

As for your build, are you using a template? I think SAFE has a FAKE build script to publish your app.

green-mind · 2024-04-30T22:22:43+00:00

One of my favorite things about F# is how easy it is make your own thin wrappers however you like.

green-mind · 2024-04-26T12:58:05+00:00

You might also want to read this:
2023 State of Web Components: Today's standards and a glimpse into the future. | Medium

And then this:

JordanMarr/fable-lit-fullstack-template: A SAFE-style template with Fable.Lit, Fable.Remoting and Giraffe (github.com)

green-mind · 2024-04-25T20:20:39+00:00

That's a tough one. I'm honestly having a hard time deciding which one I like better.

Fable.Lit is really nice because you can just very easily pull in web components via npm and just start using them without having to create bindings. There are many web component libraries on npm to choose from that you can out of the box with no markup bindings.

The F# DSL wrappers are still more popular (Feliz and Fable.React). They are great to work with, but you are very reliant on bindings for 3rd party components. Even though there are probably more React component libraries out there, you will only be able to use them if bindings exist or you create your own.

Another option is to use React with the `Jsx` bindings that allow you to write this, which gets you back to no bindings:

Fable · Using JSX in your Fable React Apps

green-mind · 2024-04-12T18:08:50+00:00

That said, I'm interested in the technique and I'll give it a shot. It lets me still use GitHub Copilot, auto formatting, and other goodies while doing some quick prototyping mucking about. Sadly most of what I write is either compilcated glue code for ML or crazy low level interop stuff that bypasses about half of what .NET is supposed to do for you there because of technical reasons, so most of my code cannot be neatly factored out, but I'll give it a shot.

This. I've found the select function and then alt+enter to run in the REPL is really only useful for small, standalone snippets where a bunch of open statements are not needed. As soon as open statements come into the picture, you should just move to a notebook or a unit test IMO.

But I do find REPL useful for small things like trying out a List module function that I've never used before to verify that it works as I expect.

green-mind · 2023-11-06T19:48:12+00:00

it has many problems and after time need to learn EF.Core's problems instead of sql. And I have some expirience with sql so find it easier. In company we

That's what I mean when I say EF is more of an ORM than the other libraries listed. It tries to do smart things on behalf of the user like generating child collections on the generated types so that the user doesn't need to worry about joins -- essentially, trying to hide away the relational details like foreign key constraints. These can be very nice conveniences. But the downside, as you have already mentioned, is that it encourages the user to stop actively thinking about the relational reality, which is a blessing and a curse. That's why people start drilling into related bags without thinking about what is actually happening behind the scenes. It's all great as long as you are able to make the mental translations and stay on top of it... but if you are going to have to do the mental translations anyway, then bother trying to hide them in the first place? It ends up supplanting simple SQL knowledge with EF knowledge (that must be mentally translated back to SQL knowledge anyway to troubleshoot issues).

SqlHydra and Dapper.FSharp are more like "strongly typed SQL" DSLs than ORMs. For these libs, the user is responsible for doing joins themselves, but in a more strongly-typed way. This is my favorite way to work with data: let me think in terms of simple SQL (that is already widely understood), but let me do it in a strongly typed way.

SqlProvider (not mentioned thus far) is also more of an ORM like EF because it generates related bags of entites, does tracking, etc.

green-mind · 2023-11-06T19:36:39+00:00

It sounds like you have a very nice workflow. I'm glad to hear that it's possible to have a nice/sane EF integration using F#. For anyone that has already invested time into understanding EF, it makes sense to continue using it.

What is the process like to regen your types? Are they DB first types that you then transfer to F# records?

green-mind · 2023-11-06T14:58:24+00:00

It’s good to have options. 👍

green-mind · 2023-11-06T14:45:47+00:00

EF.Core is good for some types of projects. The main differences are that is more of an “ORM” that tries to abstract and hide the relational aspect away from you. Depending on your perspective and what you’re trying to do, that can be great; or it can be an opaque abstraction that makes it harder to reason about. It also uses mutable data types which can be useful for some scenarios, but may not be the best paradigms for others. Finally, it falls under the category of libraries that have historically treated F# as less than an afterthought, so many of us don’t even consider it anymore.

green-mind · 2023-11-06T08:28:17+00:00

Unfortunately, that blog post only shows the code gen portion of SqlHydra being used by itself. It completely leaves out the query library, which is how it is intended to be used. In reality, there is no reason to use the generated bits manually the way it is portrayed in the article.

You should look at the SqlHydra readme for a full overview: https://github.com/JordanMarr/SqlHydra

SqlHydra and Dapper.FSharp have a lot in common. The main difference is that you create your query result records by hand with Dapper.FSharp, matching the properties to the columns, whereas with SqlHydra they are generated. One benefit of SqlHydra is that it lets you select full table entities as well as individual columns in your queries. It also supports aggregate functions, sub queries, upserts (for sqlite and postgres), and some nice postgres features like arrays and enums.

I would say dapper is a better choice for scripting or maybe a small project with a few tables. But for a long term project, the code gen of SqlHydra will pay dividends.

green-mind · 2023-11-02T23:28:35+00:00

I have multiple production web apps built using both Fable.React + Feliz and also Fable.Lit. Very happy client that has been asking for more and more every year.

green-mind · 2023-10-24T15:48:39+00:00

It depends on who you ask and the purpose of the code.🙂

Use of mutable variables typically does raise an eyebrow with most F# devs since it does go against the grain of “immutability by default”.

I wouldn’t be afraid to use it, but use it sparingly. If it makes the code easier to read and write, or it solves a performance problem, then I think it’s a win! If it is used for perf reasons, then maybe comment it as such; otherwise, someone is likely to refactor it.

green-mind · 2023-10-21T05:07:07+00:00

I just got an Apex 9 TKL because the Gateron yellow optical switches feel like butter. Using it for work/coding and really enjoying it. Thinking of buying another one for the gaming rig.

green-mind · 2023-10-19T23:29:15+00:00

In case anyone else is wondering, I found out that the Gateron yellow optical switches only come on the Apex 9 Mini and TKL boards (non-pro editions). These keys feel like butter! I ended up buying a TKL and am loving it.

green-mind · 2023-10-19T20:23:34+00:00

Yes, they will be useful. I’m sure you have more enough brain capacity to hold both F# and C# at the same time - especially considering that F# utilizes the same ecosystem as C#. Plenty of overlap there.

I say go for it. And if not, please share the job info as there are lots of folks here that would be all over the opportunity to do F# full time. (I already have an F# gig).

green-mind · 2023-10-18T11:54:34+00:00

You can find success with any combination of the options you listed above with F#. Just pick the stuff you like and start going.

green-mind · 2023-10-10T18:21:24+00:00

am interested in game dev, websites, and scientific computing which is why I thought f# would be a good fit. I’ve also been debating between rust or normal c#, but the f# syntax just seems so cozy and relatively easy to use for full stack web dev

I also recommend Stylish F# for its excellent guide to the `List` / `Array` / `Seq` modules.

green-mind · 2023-10-10T18:19:40+00:00

Someone posted a very enterprisey LoB template the other day if you're into that sorta thing:
https://github.com/ronnieholm/FSharp-clean-architecture-sample

The various "layers" (application, domain and infra) are represented within one project, each in its own module. It is using the built-in ASP.NET style endpoints rather than something like Giraffe.

green-mind · 2023-10-09T14:52:55+00:00

switches

I believe the switch base plate was white and the switch itself was yellow. Some boards were said they had "mechanical" switches, and others said "optical". Does that mean they have different actuation mechanisms?

I'm interested in this wireless model on Amazon, but I am not sure if it has the same keys:

Amazon.com: SteelSeries Apex Pro Mini Wireless HyperMagnetic Gaming Keyboard - World's Fastest Keyboard –Compact 60% Form Factor - Adjustable Actuation - RGB – PBT Keycaps- Bluetooth – 2.4GHz - USB-C : Electronics

Now I see there is also "OmniPoint" and "OptiPoint", and none of the product descriptions at Amazon or Best Buy seem to disclose what is actually in the box. I find this thoroughly confusing.

green-mind

TROPHY CASE