-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Announcement) Version 4 development #71
Labels
announcement
Something big to announce
Comments
Merged
Version 4 released |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From the first line of the code, my idea behind
Dapper.FSharp
was to create a simple and straightforward abstraction over SQL queries people tend to use most of the time. Initial idea was to create a single abstraction to cover the top three used SQL-based databases: MSSQL, MySQL, and PostgreSQL. Such a decision played well at the very beginning, but over time, and with a growing user base, there were many PRs to add more and more DB vendor-related features (e.g. #61, #65, or #70) which I had to reject for the sake of unified abstraction - I simply couldn't add features that would work only for one of the databases. And trust me on this - it never felt good to reject well-intended PRs.So... I decided to start working on v4, which will be refactored from the ground. The main goals of this breaking change are:
Dapper.FSharp.MSSQL
)Deconstructor
and its functionalityETA: End of 2022, but no promises here...
The text was updated successfully, but these errors were encountered: