JDBI VS Entity Framework

While this may work for greenfield applications, I don't see this working well for preexisting schemas. From their getting started page: "Database fields are automatically created for any abstract getter methods", which definitely scares me away since they seem to be relying on automatic field type conversions. I prefer to manage my schemas when I can and do type and DAO conversions via mapper classes in the very... - Source: Hacker News / 8 months ago

Someone else mentioned jOOQ, but personally I also rather enjoyed JDBI3: https://jdbi.org/#_introduction_to_jdbi_3 It addresses the issues with using JDBC directly (not nice ergonomics), while still letting you work with SQL directly without too many abstractions in the middle. In combination with Dropwizard, it was pretty pleasant: https://www.dropwizard.io/en/stable/manual/jdbi3.html Other than that, I actually... - Source: Hacker News / 8 months ago

> I've been doing ORM on Java since Hibernate was new, and it has always sucked. Have you ever looked at something like myBatis? In particular, the XML mappers: https://mybatis.org/mybatis-3/dynamic-sql.html Looking back, I actually quite liked it - you had conditionals and ability to build queries dynamically (including snippets, doing loops etc.), while still writing mostly SQL with a bit of XML DSL around it,... - Source: Hacker News / 10 months ago

I found JDBi[1] to be a really nice balance between ORM and raw SQL. It gives me the flexibility I need but takes care of a lot of the boilerplate. It's almost like a third category. 1. http://jdbi.org. - Source: Hacker News / 11 months ago

You could use something like jdbi or mybatis. It's not as ugly as raw jdbc and easier to use without all of the gunk from an ORM like hibernate. Source: about 1 year ago

I only wanted to give a simple preview of what can be done with Entity Framework, but if this is something that interests you and you want to go further in-depth with all the possibilities, I recommend checking out the official docs where you can also find a great tutorial which will guide you through building your very own .NET Core web application. - Source: dev.to / 11 months ago

Entity Framework documentation hub - Entity Framework is a modern object-relation mapper that lets you build a clean, portable, and high-level data access layer with .NET (C#) across a variety of databases, including SQL Database (on-premises and Azure), SQLite, MySQL, PostgreSQL, and Azure Cosmos DB. It supports LINQ queries, change tracking, updates, and schema migrations. Source: 11 months ago

You can create the DAL using your existing code or start using a Object Relational Mapper like Entity Framework which will do a lot of the work for you, check this out here: https://learn.microsoft.com/en-us/ef/ also check out LINQ. Source: about 1 year ago

And, possibly (not strictly speaking necessary but very useful) Entity framework as a backend part of it. Source: about 1 year ago

EF is a library written by Microsoft themselves no less, and provided totally for free under a permissive open source license. And not only do Microsoft engineers continue to work on it (and have been continuously since EF Core 1 back in 2017), tons of non-MS coders have contributed code, bug fixes and raised issues. Probably millions of dollars of dev time have been poured into EF. There's massive amounts of... Source: about 1 year ago