ormlite
JDBI
ormlite | JDBI | |
---|---|---|
2 | 27 | |
1,579 | 1,905 | |
- | 0.5% | |
0.0 | 9.4 | |
about 1 year ago | 17 days ago | |
Java | Java | |
ISC License | Apache 2.0 license |
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.
ormlite
-
Struggling from imposter syndrome
I am doing an internship as a mobile application developer. The technologies used in my company are Java in android studio, SQLite, Retrofit, Volley, and Orm - lite. I started to learn how to work with these libraries and databases in android studio. But I couldn't able to understand the concept of orm-lite yet. I've read the official documentation and other resources. Asked for help from my seniors. But every time I asked for help they show me code how they work with orm-lite and say this is easy. This is the fourth month of my internship. But I still couldn't understand how to work with orm-lite. Because of that, they didn't give me any tasks for me. This is really annoying situation for me. I think now I am exposed to imposter syndrome. I am really frustrated at this moment. If anyone in this group has faced a situation like this. How did you get away with it?
-
What are some more options or good practices for dynamic SQL query building?
I liked this one https://ormlite.com/
JDBI
-
Permazen: Language-natural persistence to KV stores
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 simple and elegant JDBI framework where you write SQL annotations above your DAO methods https://jdbi.org/#_declarative_api
JDBI does wonders for wonky old schemas you've inherited, since joins etc work out of the box (just throw them in your annotations!) The annotations can also link to .SQL files for the big hairy queries.
All these "do magic" frameworks (hibernate being one of the first) work in the simple cases but then fall apart whenever you need to do anything complex/not-prescribed. I end up having to dig into the internals of the framework to see what's going wrong which negates their whole value add.
-
Is ORM still an anti-pattern?
> 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, which didn't suck as much as one might imagine. The only problem was that there was still writing some boilerplate, which I wasn't the biggest fan of.
Hibernate always felt like walking across a bridge that might collapse at any moment (one eager fetch away from killing the performance, or having some obscure issue related to the entity mappings), however I liked tooling that let you point towards your database and get a local set of entities mapped automatically, even though codegen also used to have some issues occasionally (e.g. date types).
That said, there's also projects like jOOQ which had a more code centric approach, although I recall it being slightly awkward to use in practice: https://www.jooq.org/ (and the autocomplete killed the performance in some IDEs because of all the possible method signatures)
More recently, when working on a Java project, I opted for JDBI3, which felt reasonably close to what you're describing, at the expense of not being able to build dynamic queries as easily, as it was with myBatis: https://jdbi.org/
That said, with the multi-line string support we have in Java now, it was rather pleasant regardless: https://blog.kronis.dev/tutorials/2-4-pidgeot-a-system-for-m...
I don't think there's a silver bullet out there, everything from lightweight ORMs, to heavy ORMs like Hibernate, or even writing pure SQL has drawbacks. You just have to make the tradeoffs that will see you being successful in your particular project.
-
Sketch of a Post-ORM
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
- Is it just me, or does the Spring Framework lead to hard-to-maintain code and confusion with annotations?
-
Can someone tell me a good resource to learn and practice JDBC in java?
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.
-
Which JVM Language Would You Choose for a New Server-Side Project?
We use JDBI. Very simple and lightweight. It uses an object mapper not a full fledged ORM.
-
Why people don't like Java?
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.
-
Top 5 Server-Side Frameworks for Kotlin in 2022: Micronaut
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.
-
Fiz um mapa interativo com os resultados do segundo turno do STE com postgres (+postgis) e openlayers
Ah! E sobre o que eu usei no backend, alem de postgres e fly.io, o backend eh eh Java, usando um framework chamado quarkus e jdbi pra fazer a interface com o banco.
-
Is JDBC becoming a “legacy” API??
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.
What are some alternatives?
Realm - Realm is a mobile database: a replacement for SQLite & ORMs
jOOQ - jOOQ is the best way to write SQL in Java
greenDAO - greenDAO is a light & fast ORM solution for Android that maps objects to SQLite databases.
Spring Data JPA - Simplifies the development of creating a JPA-based data access layer.
sugar - Insanely easy way to work with Android Database.
HikariCP - 光 HikariCP・A solid, high-performance, JDBC connection pool at last.
ActiveAndroid - Active record style SQLite persistence for Android
sql2o - sql2o is a small library, which makes it easy to convert the result of your sql-statements into objects. No resultset hacking required. Kind of like an orm, but without the sql-generation capabilities. Supports named parameters.
DBFlow - A blazing fast, powerful, and very simple ORM android database library that writes database code for you.
Querydsl - Unified Queries for Java
android-database-sqlcipher - Android SQLite API based on SQLCipher
Flyway - Flyway by Redgate • Database Migrations Made Easy.