EntityFramework.DatabaseMigrator VS SQLProvider

Compare EntityFramework.DatabaseMigrator vs SQLProvider and see what are their differences.

EntityFramework.DatabaseMigrator

EntityFramework.DatabaseMigrator is a WinForms utility to help manage Entity Framework 6.0+ migrations. (by TheOtherTimDuncan)
ORM

SQLProvider

A general F# SQL database erasing type provider, supporting LINQ queries, schema exploration, individuals, CRUD operations and much more besides. (by fsprojects)
Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
EntityFramework.DatabaseMigrator SQLProvider
- 9
4 558
- 1.8%
0.0 8.5
about 8 years ago 10 days ago
C# F#
Apache License 2.0 GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

EntityFramework.DatabaseMigrator

Posts with mentions or reviews of EntityFramework.DatabaseMigrator. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning EntityFramework.DatabaseMigrator yet.
Tracking mentions began in Dec 2020.

SQLProvider

Posts with mentions or reviews of SQLProvider. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-10-28.
  • Warning FS0101: This API supports the FSharp.Data.SqlClient...
    3 projects | /r/fsharp | 28 Oct 2022
    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?
    4 projects | /r/fsharp | 10 Jul 2022
    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 ?
    7 projects | /r/dotnet | 2 Apr 2022
    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
    2 projects | /r/fsharp | 20 Oct 2021
    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
    9 projects | news.ycombinator.com | 17 Oct 2021
    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
    5 projects | news.ycombinator.com | 28 Aug 2021
    (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
    3 projects | /r/dotnet | 27 Aug 2021
    Like this?
  • Getting SQL Provider to work with PostgreSQL
    1 project | /r/fsharp | 19 Mar 2021
    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
    2 projects | /r/fsharp | 6 Mar 2021
    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?

When comparing EntityFramework.DatabaseMigrator and SQLProvider you can also consider the following projects:

FluentMigrator - Fluent migrations framework for .NET

Dapper - Dapper - a simple object mapper for .Net [Moved to: https://github.com/DapperLib/Dapper]

ServiceStack.OrmLite - Fast, Simple, Typed ORM for .NET

Entity Framework - EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.

BL Toolkit - Business Logic Toolkit for .NET

Dapper.FastCRUD - fast & light .NET ORM for strongly typed people

NPoco - Simple microORM that maps the results of a query onto a POCO object. Project based on Schotime's branch of PetaPoco

LINQ to DB - Linq to database provider.

PetaPoco - Official PetaPoco, A tiny ORM-ish thing for your POCO's

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.