JDBI VS Hibernate ORM

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 / 7 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 / 7 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

Postgres-based persistence with a pretty straightforward mapping of SQL queries to Clojure functions. If you have ever used Java with Hibernate ORM for data persistence, you will feel relief after working with the database in Clojure with Hugsql. The model of the persistence layer is much simpler and easier to understand without the need for Session Cache, Application Level Cache and Query Cache. Debugging is... - Source: dev.to / about 1 hour ago

This is so close to perfection. For me though application shouldn't have a coupling with entity framework. If you wanted to switch out EF to use hibernate (https://hibernate.org/orm/)? you're application is coupled to EF and would require a lot more work. Source: about 1 year ago

Hibernate is the umbrella for a collection of libraries, most notably Hibernate ORM which provides Object/Relational Mapping for java domain objects. In addition to its own "native" API, Hibernate ORM is also an implementation of the Java Persistence API (jpa) specification. - Source: dev.to / over 1 year ago

You may be familiar with the Hibernate ORM, an implementation of the Java Persistence API (JPA) specification. - Source: dev.to / over 1 year ago

This article gets you started with the Hibernate implementation of JPA. We’ll use only standard features and cover only the basics. If you are looking for a comprehensive course on JPA or Hibernate, I recommend reading the JPA spec and the official Hibernate docs. - Source: dev.to / about 2 years ago