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
We use JDBI. Very simple and lightweight. It uses an object mapper not a full fledged ORM. Source: about 1 year ago
Alternatively there are... Hybrid solutions like Kotlin's https://github.com/JetBrains/Exposed or https://jdbi.org/ that don't quite... Do all the heavy lifting for querying but allow you to sorta stitch queries together manually. Source: about 1 year ago
As seems that Micronaut does not include anything similar by default, we use JDBI and that SQL to retrieve one random greeting from the greetings table. - Source: dev.to / over 1 year ago
More personally, I'm not much an ORM guy. I've just never found that the benefits outweigh the costs, but that's just my opinion. That said, I don't use JDBC directly in my own projects anymore, strongly preferring to use JDBI instead. I find that it walks the line between "make using the database easier" and "get between you and the database" beautifully. But there's not a darn thing wrong with using JDBC directly. Source: over 1 year ago
I really like JDBI. It’s thin enough that it lets you do anything SQL can do, but opinionated enough to provide a sane, sturdy, structured approach to working with a database. Source: over 1 year ago
JDBI - shares features/ideas with many others but is the best of breed. Source: over 1 year ago
For data, we use S3/MinIO, sharded PostgreSQL, and Elasticsearch. For accessing the database, we don't use Java Persistence API (JPA) but JDBI.org as it is easier to tweak queries manually, and we use a lot of specific queries and offload some processing to the database. Many of them are written to use PostgreSQL's specific features, e.g., JSONB columns, so we don't consider database independence a critical factor. - Source: dev.to / almost 2 years ago
Another option is JDBI, that helps you with mappings too while having less features than JPA: https://jdbi.org/. Source: almost 2 years ago
Hi! I’m not familiar with this particular exception in combination with Micronaut, because my team has chosen to use JDBI rather than Hibernate. Source: almost 2 years ago
By the way, you probably don't need Spring Data and Hibernate, if you apply the Transaction Script pattern. Since all business rules are bound to services, Hibernate will bring overhead and not so many benefits. Instead, you could try to use JDBI, JOOQ or even plain JDBC. - Source: dev.to / over 2 years ago
I really like Jdbi which I feel has a very similar goal than your library. Source: over 2 years ago
There are plenty of alternatives to ORMs. We use JDBI (https://jdbi.org) which is dead simple and a happy medium between pure JDBC and a full blown ORM. Even using the built-in JDBC support is an option with modern Java, PreparedStatement and ResultSet implement AutoClosable, which means you can write code like this:- Source: Hacker News / over 2 years agotry (.
Ideally I'd like to use something like https://jdbi.org/ - ORM which only does conversion from rows to objects, no other magic. But I don't think it exists for node. Source: almost 3 years ago
* ... At least for Java and Kotlin the awesome library jdbi ( https://jdbi.org/ ) implements a very useful hybrid approach. One creates DAOs and Repositories to abstract away the DB and map results and arguments to/from objects on the fly. All while retaining full control over the SQL and all mapping aspects. This way SQL and mapping can be optimized to leverage the features of each database (ie.... - Source: Hacker News / almost 3 years ago
I used to be in the camp of "ORM's are bad just write your own queries" but once the application grows to some extent and you are interacting with several rows of data across many different tables often you'll wish you had an ORM (or at the very least a SQL builder or even something ORM like but hand-written like https://jdbi.org/#_createsqlobject ). Source: almost 3 years ago
No dice. From the docs (https://jdbi.org/#_primitive_mapping):. Source: almost 3 years ago
Do you know an article comparing JDBI to other products?
Suggest a link to a post with product alternatives.
This is an informative page about JDBI. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.