MiniScaffold
SQLProvider
Our great sponsors
| MiniScaffold | SQLProvider | |
|---|---|---|
| 2 | 9 | |
| 268 | 558 | |
| - | 1.8% | |
| 7.4 | 8.4 | |
| 5 months ago | 7 days ago | |
| F# | F# | |
| MIT License | GNU General Public License v3.0 or later |
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.
MiniScaffold
-
Structure of .NET Core open source F# projects
Thanks, this looks like exactly the sort of thing I'm looking for. (Link for others who might be interested.)
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!
-
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.
-
EF vs Dapper - a false dilemma
Like this?
-
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?
What are some alternatives?
Dapper - Dapper - a simple object mapper for .Net [Moved to: https://github.com/DapperLib/Dapper]
Entity Framework - EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.
Dapper.FastCRUD - fast & light .NET ORM for strongly typed people
LINQ to DB - Linq to database provider.
PetaPoco - Official PetaPoco, A tiny ORM-ish thing for your POCO's
EntityFramework.DatabaseMigrator - EntityFramework.DatabaseMigrator is a WinForms utility to help manage Entity Framework 6.0+ migrations.
TypeORM - ORM for TypeScript and JavaScript. Supports MySQL, PostgreSQL, MariaDB, SQLite, MS SQL Server, Oracle, SAP Hana, WebSQL databases. Works in NodeJS, Browser, Ionic, Cordova and Electron platforms.
JsonFlatFileDataStore - Simple JSON flat file data store with support for typed and dynamic data.
ServiceStack.OrmLite - Fast, Simple, Typed ORM for .NET
Marten - .NET Transactional Document DB and Event Store on PostgreSQL
Fluent NHibernate - Fluent NHibernate!
Tortuga Chain - A fluent ORM for .NET