SQLProvider
Dapper.FSharp
SQLProvider | Dapper.FSharp | |
---|---|---|
9 | 7 | |
558 | 361 | |
0.7% | - | |
8.5 | 4.8 | |
12 days ago | about 1 month ago | |
F# | F# | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
SQLProvider
-
Warning FS0101: This API supports the FSharp.Data.SqlClient...
For completeness, there is also the SqlDataProvider, which I only tried out a little years ago, before composibility was baked in. Worth a look.
-
Is there a market for a complete fsharp ORM library?
Have you heard of type providers? https://fsprojects.github.io/SQLProvider/ I think this library might be what you are looking for
-
If you were to create a Web API today from scratch how would you do it ?
Database: SQL or Event Store. If SQL, One of https://fsprojects.github.io/SQLProvider/, https://github.com/Dzoukr/Dapper.FSharp or https://github.com/SQLStreamStore/SQLStreamStore
-
What's new in F# 6
One of the more popular Type Providers I used is the SQL Provider, but even it has severe limitations when it comes to .NET Core.
-
Fable is a compiler that brings F# into the JavaScript ecosystem
There was a wave of popularity in 2017 as well. I used to work on it full time back then, and enjoyed it a lot. The SQLProvider [0] and other type providers like it are super impressive!
[0] https://fsprojects.github.io/SQLProvider/
-
Weird
(1) F# Type Providers still blow my mind.
Strongly typed SQL/XML/CSV/JSON without boilerplate is a massive leap forward, and it's a shame that it hasn't caught on.
https://fsprojects.github.io/SQLProvider/#Example
-
EF vs Dapper - a false dilemma
Like this?
-
Getting SQL Provider to work with PostgreSQL
So... I'm a little bit lost here. I must say, I love this language, but documentation is definitely not its greatest strength. I've looked at the SQLProvider documentation and found no information. Then I looked through the repository issues and found a lot of people with similar issues and, even though they should theoretically be solved with version 1.2, I tried doing what ended up working for them, with little luck. I've tried different combinations of library targets and dependencies versions but none worked.
-
Structure of .NET Core open source F# projects
So when I clone a typical open source F# project from GitHub (e.g. SQLProvider, to pick a recent one that I wrestled with), I'm often at a loss how to build and debug the thing. I've figured out that running build.cmd is usually a good place to start, but then what? Can I still open the .sln in Visual Studio and build/debug it there?
Dapper.FSharp
-
No pure fsharp orm?
What about Dapper.FSharp?
- Idiomatic way to interact with database
-
Warning FS0101: This API supports the FSharp.Data.SqlClient...
Dapper FSharp is quite popular and worth checking out.
-
Is there a market for a complete fsharp ORM library?
I have been looking for frameworks to work with databases in f# and found some reasonable. My favorite so far is Dapper.FSharp. It's a very nice CRUD helper. I looked for some 'fsharp helper' for EF and found EFCore.FSharp which does not support discriminated unions unfortunately and does not go very far. I was intrigued by Litedb.FSharp but I would like to stick with sql databases.
-
If you were to create a Web API today from scratch how would you do it ?
Database: SQL or Event Store. If SQL, One of https://fsprojects.github.io/SQLProvider/, https://github.com/Dzoukr/Dapper.FSharp or https://github.com/SQLStreamStore/SQLStreamStore
- Best practices F# API?
-
Data Access in Fsharp
They are slightly different and depending on your background one might feel more confortable than the other Feel free to choose the one you like the best, in my case I will continue the rest of the post with the Expression based one given that we already have some expression based code from Dapper.FSharp. Previously we added some authors, let'ts try to add Posts to those authors with Donald.
What are some alternatives?
Dapper - Dapper - a simple object mapper for .Net [Moved to: https://github.com/DapperLib/Dapper]
SqlHydra - SqlHydra is a suite of NuGet packages for working with databases in F# including code generation tools and query expressions.
Entity Framework - EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.
Npgsql.FSharp - Thin F# wrapper around Npgsql, the PostgreSQL database driver for .NET
Dapper.FastCRUD - fast & light .NET ORM for strongly typed people
Rezoom.SQL - Statically typechecks a common SQL dialect and translates it to various RDBMS backends
LINQ to DB - Linq to database provider.
Donald - A lightweight, generic F# database abstraction.
EntityFramework.DatabaseMigrator - EntityFramework.DatabaseMigrator is a WinForms utility to help manage Entity Framework 6.0+ migrations.
Npgsql.FSharp.Analyzer - F# analyzer that provides embedded SQL syntax analysis, type-checking for parameters and result sets and nullable column detection when writing queries using Npgsql.FSharp.
PetaPoco - Official PetaPoco, A tiny ORM-ish thing for your POCO's
VisualFSharp - The F# compiler, F# core library, F# language service, and F# tooling integration for Visual Studio