SqlKata Query Builder
honeysql
Our great sponsors
SqlKata Query Builder | honeysql | |
---|---|---|
5 | 16 | |
2,978 | 1,698 | |
1.5% | - | |
3.0 | 8.6 | |
5 days ago | 20 days ago | |
C# | Clojure | |
MIT 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.
SqlKata Query Builder
-
EF Core or Dapper
SqlKata is your friend.
-
ASP.Net Core database modelling without using existing ORMs?
Don't know if can be a good pick for the no-ORM requirement but I would take a look at SqlKata which is a nice query builder + execution engine, built on top of Dapper
-
Windyquery: A non-blocking Python PostgreSQL query builder
That is basically the description of an object mapper, with all the guarantees of an object mapper :). It seems if you actually use the query builder as such, no guarantees exist.
I'm pretty picky regarding query builders and ORM's, to the extent of having written several of them over the years, in different languages (both dynamic and strong typed, unfortunately closed-source). I'm a strong advocate of schema-first design, and usually a query builder will allow you to design your queries explicitly, but having some internal behaviors (such as string concatenation, identifier quoting and automatic in-order separation of parameters and values to be bound) taken care of. As good examples of this, I'd mention golang's goqu (https://github.com/doug-martin/goqu) and - to some extent - C# SqlKata (https://sqlkata.com/). Following my frustrations with Python ORMs, I built my own toy project, sort-of-in-beta, called rickdb (https://github.com/oddbit-project/rick_db).
-
I don't want to learn your garbage query language
Less about the exact syntax and more about the tool, for example: https://github.com/sqlkata/querybuilder. I just chose that since it was on top of a search but the idea is the same. Your code generates raw SQL, so it's 100% interchangeable with writing SQL yourself however the builder library deals with the syntax, proper ordering, quoting, full attribute names, etc. Some such libraries even let you define your schema in code to make your SQL generation type safe.
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
-
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].
SQL was meant to be a hosted language from the get-go though, so any kind of macro-like feature was expected to be done in the host language.
Of course it's a bit painful and error prone, given SQL is a textual language, but as HoneySQL (https://github.com/seancorfield/honeysql) shows, you can represent SQL statements as data and generate them programmatically in a safe manner.
-
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.
-
Successors to Korma?
HoneySQL is an SQL query generation and manipulation library based on nested Clojure data structures that can be rendered into SQL.
What are some alternatives?
Yessql - A .NET document database working on any RDBMS
NReco LambdaParser - Runtime parser for string expressions (formulas, method calls). Builds dynamic LINQ expression tree and compiles it to lambda delegate.
MongoDB - The MongoDB Database
LiteDB - LiteDB - A .NET NoSQL Document Store in a single data file
Insight.Database - Fast, lightweight .NET micro-ORM
sqlx - general purpose extensions to golang's database/sql
monitor-table-change-with-sqltabledependency - Get SQL Server notification on record table change
hugsql - A Clojure library for embracing SQL
Streamstone - Event store for Azure Table Storage
Realm Xamarin - Realm is a mobile database: a replacement for SQLite & ORMs
Apache Ignite - Apache Ignite
SQLStreamStore - Stream Store library targeting RDBMS based implementations for .NET