spring-data-relational
honeysql
spring-data-relational | honeysql | |
---|---|---|
11 | 16 | |
728 | 1,705 | |
-0.4% | - | |
9.1 | 8.6 | |
7 days ago | 11 days ago | |
Java | Clojure | |
Apache License 2.0 | - |
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.
spring-data-relational
-
You might not need an ORM
What do you think of Spring Data JDBC (https://spring.io/projects/spring-data-jdbc)?
-
Architecture Pitfalls: Don’t use your ORM entities for everything — embrace the SQL!
What do you think of Spring Data JDBC?
-
Where is the Lock annotation in Spring-data-jdbc?
Link to GitHub: https://github.com/spring-projects/spring-data-relational/blob/main/spring-data-relational/src/main/java/org/springframework/data/relational/repository/Lock.java
-
What are some more options or good practices for dynamic SQL query building?
I would ignore the hipster jOOQ and similar and start with Spring Data JDBC https://spring.io/projects/spring-data-jdbc
-
Which ORM framework are you using with Java, and why?
This makes Spring Data JDBC a simple, limited, opinionated ORM.
-
Solution to NullPointerException in java?
Though JPA is fine, and yes hibernate can be used under the hood. When it comes to spring it is mostly what level of abstraction you want. Or you could go with JDBC. And you have a spring data JDBC for having a similar abstraction as to the JPA one.
- Is there a reason to not use Spring Data JPA and Jackson in big projects?
-
Jodd – The Unbearable Lightness of Java
This is not correct. You're thinking Spring Data JPA [1]. Spring Data JDBC [2] does _not_ use any Hibernate nonsense.
[1] https://spring.io/projects/spring-data-jdbc
-
I wrote an MVP in Java and it was actually pleasant
The data moved from the awesome-but-confusing DynamoDB... into PostgreSQL✨, using Spring Data JDBC.
-
20 years of Hibernate
I didn't have much experience with Hibernate and Spring (was using JavaEE prior), it could very possibly be the case, that the team simply misused Hibernate. We might have used n+1 queries, eager loading (although I mildly remember we fixed this), oh and we had the old id generation via sequence in Hibernate, that was really pain to optimize properly. Oracle 11 does not have identity generation. I remembered this only becuase I created an issue at the time. Still not implemented, but can't blame them, who the hell uses sequences as ID generation nowadays.
honeysql
-
Why Is Jepsen Written in Clojure?
I recall using korma way back I and I don’t recall it being terrible but I would say https://github.com/seancorfield/honeysql has very much superseded it by this point… (but I can see how that might not be obviously clear if one is to look at superficial metrics like GitHub stars for example…)
-
That's a Lot of YAML
Joins can certainly work in a data format like YAML. For an example, see Honey SQL from the Clojure community [0] (though without something to contrast strings like Clojure's keywords, you miss out on the automatic parameterization).
You mentioned moving JOINs around, so I'll mention that if represented as structured data, you can move any of the top level components around, so you could more closely follow the "true order of SQL" [1]. For example, I would love to be able to put FROM before SELECT in all or almost all cases. There's also being able to share and add to something like a complicated WHERE clause, where essentially all programming languages have built-in facilities for robustly manipulating ordered and associative data compared to string manipulation, which is not well-suited for the task.
Now don't get me wrong, I don't particularly care for YAML (though it doesn't bother me that much), but as someone who's done their fair share of programmatic SQL creation and manipulation in strings, not having a native way to represent SQL as data is a mistake in my opinion.
0: https://github.com/seancorfield/honeysql#big-complicated-exa...
- Como desenvolvi um backend web em Clojure
-
XTDB 2.x Early Access
In Clojure-land, we are also using HoneySQL [1] which has similar characteristics. You are still working within SQL semantics so it's a bit more complicated, but we are doing great complicated things with just maps, no API necessary.
[1] https://github.com/seancorfield/honeysql
-
Run SQL queries against your system and get back structured data using osquery and Babashka
using honeysql we can make structured queries as well
-
Some questions regarding developing simple web apps in Clojure from a Clojure "beginner"
As someone else already pointed out, next.jdbc is good for database connectivity (for Postgres and beyond). For composing the queries themselves, I strongly recommend Honey SQL. It lets you represent queries themselves as normal Clojure data structures, just vectors and maps.
- What are some more options or good practices for dynamic SQL query building?
-
Ask HN: Does anyone else think SQL needs help?
Perhaps you're looking for a way of arranging SQL as an AST represented by data structures (or objects) that can be fed to a compiler. HoneySQL[0] is one such implementation of this idea and it makes your general transformation trivial for Clojure programs. You don't need to mess around with string concatenation because you have a predictable and extensible compiler for data structures (which are themselves easily composable/transformable/storable with Clojure) that you can trust to do the right thing. If you're using some weird database or need an esoteric syntax, extending the compiler to your clause is easy to do[1].
[0] https://github.com/seancorfield/honeysql
[1] https://github.com/seancorfield/honeysql#extensibility
-
Lisp feature - domain specific language
https://github.com/seancorfield/honeysql (write SQL without having to write SQL)
-
Fly.io Buys Litestream
I've used it from Clojure, via HoneySQL, so no ORM, no danger of SQL injection. It was really wonderful!
https://github.com/seancorfield/honeysql
I used it to quickly iterate on the development of migration SQL scripts for a MySQL DB, which was running in production on RDS.
I might have switched to H2 DB later, because that was more compatible with MariaDB, but I could use the same Clojure code, representing the SQL queries, because HoneySQL can emit different syntaxes.
What are some alternatives?
MyBatis - MyBatis SQL mapper framework for Java
hugsql - A Clojure library for embracing SQL
high-performance-java-persistence - The High-Performance Java Persistence book and video course code examples
SqlKata Query Builder - SQL query builder, written in c#, helps you build complex queries easily, supports SqlServer, MySql, PostgreSql, Oracle, Sqlite and Firebird
JDBI - The Jdbi library provides convenient, idiomatic access to relational databases in Java and other JVM technologies such as Kotlin, Clojure or Scala.
malli - High-performance data-driven data specification library for Clojure/Script.
jodd-json - JSON Java serializer and parser.
pggen - Generate type-safe Go for any Postgres query. If Postgres can run the query, pggen can generate code for it.
nanohttpd - Tiny, easily embeddable HTTP server in Java.
missionary - A functional effect and streaming system for Clojure/Script
Ebean ORM - Ebean ORM
awesome-clojure - A curated list of awesome Clojure libraries and resources. Inspired by awesome-... stuff