coffee4j-back-end
jOOQ
| coffee4j-back-end | jOOQ | |
|---|---|---|
| 1 | 97 | |
| 0 | 6,180 | |
| - | 0.4% | |
| 10.0 | 9.8 | |
| over 1 year ago | 3 days ago | |
| Java | Java | |
| MIT License | GNU General Public License v3.0 or later |
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.
coffee4j-back-end
-
Are there any poplar alternatives to siesta?
Yeah, give it a shot! Before this, I added custom hints like this. I still need to try using the reachability repo instead
jOOQ
-
Net 9.0 LINQ Performance Improvements
jOOQ would be one such example, https://www.jooq.org/
Not that I use this, I am a myBatis person in what concerns database access in Java, and Dapper in .NET for that matter, not a big ORM fan.
- Sqlc: Compile SQL to type-safe code
-
Serious flaws in SQL – Edgar F. Codd (1990)
> 2. ORMs do not hide SQL nastiness.
This is certainly true!
I mean: ORMs are now well known to "make the easy queries slightly more easy, while making intermediate queries really hard and complex queries impossible".
I think the are of ORMs is over. It simply did not deliver.
If a book on SQL is --say-- 100 pages, a book on Hibernate is 400 pages. So much to learn just to make the easy queries slightly easier to type? Just not worth it.
I prefer jooq any day over ORMs. And dont get me started over what tools like Hasuna have to offer.
There are also some languages (forgot the names) that are SQL-done-right. Select in the back, more type safe, more logic, more in the same steps as the query gets executed. These need to be adopted by PG and MySQL and we're good to go. (IMHO)
https://www.jooq.org/
https://hasura.io/
- ORMs are nice but they are the wrong abstraction
-
Do jOOQ DAOs support Kotlin Coroutines with R2DBC?
See: https://github.com/jOOQ/jOOQ/issues/5916
- Ask HN: What's your experience with stored procedures-heavy systems?
- SQL based language for the SQL impaired?
-
Spring boot ili asp.net core?
Spring Boot, ili ako bi nesto vise lightweight u Javi Spark + jOOQ
- Is ORM still an anti-pattern?
-
SQL-Parsing
Have a look at jooq - I know this has been used to rewrite SQL from one dialect to another, so it MUST be capable of collating code activity metrics. Look here. Otherwise, you might want to look into writing your own parser. ANTLR has a T-SQL dialect parser script here.
What are some alternatives?
juery - Juery is a tiny Java library to manage search and filter query from user to database.
Querydsl - Unified Queries for Java
graalvm-reachability-metadata - Repository which contains community-driven collection of GraalVM reachability metadata for open-source libraries.
JDBI - The Jdbi library provides convenient, idiomatic access to relational databases in Java and other JVM technologies such as Kotlin, Clojure or Scala.
daobab-100plus-examples - Daobab examples in Java
Spring Data JPA - Simplifies the development of creating a JPA-based data access layer.
siesta - Typesafe API for SQL
HikariCP - 光 HikariCP・A solid, high-performance, JDBC connection pool at last.
vertx-jooq - A jOOQ-CodeGenerator to create vertx-ified DAOs and POJOs.
Speedment - Speedment is a Stream ORM Java Toolkit and Runtime
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.
SQLDelight - SQLDelight - Generates typesafe Kotlin APIs from SQL