core.async
honeysql
core.async | honeysql | |
---|---|---|
9 | 16 | |
1,934 | 1,705 | |
-0.2% | - | |
5.1 | 8.6 | |
3 months ago | 15 days ago | |
Clojure | Clojure | |
Eclipse Public License 1.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.
core.async
-
How to handle concurrency in Clojure with core.async
Hey, how you doing? This article was written right after I had to painstakingly read the clojure.core.async source code in order to finish a task. So, I hope I save you from the same fate as I had 😄.
- Como desenvolvi um backend web em Clojure
-
Comparison of manifold and clojure.core.async
It was created by Rich Hickey: https://github.com/clojure/core.async/commit/47b1d24c0291050a1188dbeee2fc9227f694eb3c don't think he's disavowed it lol.
-
Sleeping is not the best option
Some time ago we developed some helpers using the capturing notifications strategy to test asynchronous ClojureScript code that was using core.async channels. Have a look at, for instance, the expect-async-message assertion helper in which we use core.async/alts! and core.async/timeout to implement this behaviour. The core.async/alts! function selects the first channel that responds. If that channel is the one the test code was observing we assert that the received message is what we expected. If the channel that responds first is the one generated by core.async/timeout we fail the test. We mentioned these async-test-tools in previous post: Testing Om components with cljs-react-test.
-
What is the difference between Manifold and core.async?
Hi there I'm using Clojure almost a year. I've played with both Manifold and core.async a bit but I'm not %100 sure when to use core.async over Manifold or vice versa.
-
Rich Hickey – open-source is Not About You
If you're not familiar with lisps in general, it might be hard to grok the differences between lisp-macros (as used in Clojure) and "normal" macros you see in other languages.
But, if you are familiar already, and just wanna see examples of neat macros that makes the API nicer than what a function could provide, here are a few:
- https://github.com/clojure/core.async/blob/master/examples/w...
- https://github.com/weavejester/compojure
- https://github.com/ptaoussanis/timbre
- https://github.com/krisajenkins/yesql
-
The Clojure Mindshare (2019)
https://github.com/clojure/core.async
> and with a very poor tooling (lack of IDE's)
Lisps have fantastic support in Emacs and VSCode and are in general simple enough languages that often the heavyweight of an IDE is not needed. But if you want IDEs there are:
- 6 Years of Professional Clojure
-
Equivalent of select in core.async?
If you don't want to block the current thread, you can do the looking/waiting on another thread via thread or in a go using alts! .
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?
promesa - A promise library & concurrency toolkit for Clojure and ClojureScript.
hugsql - A Clojure library for embracing SQL
cloroutine - Coroutine support for clojure
SqlKata Query Builder - SQL query builder, written in c#, helps you build complex queries easily, supports SqlServer, MySql, PostgreSql, Oracle, Sqlite and Firebird
zio-schema - Compositional, type-safe schema definitions, which enable auto-derivation of codecs and migrations.
malli - High-performance data-driven data specification library for Clojure/Script.
lein-ancient - Check your Projects for outdated Dependencies
pggen - Generate type-safe Go for any Postgres query. If Postgres can run the query, pggen can generate code for it.
yesql - A Clojure library for using SQL.
missionary - A functional effect and streaming system for Clojure/Script
shadow-cljs - ClojureScript compilation made easy
awesome-clojure - A curated list of awesome Clojure libraries and resources. Inspired by awesome-... stuff