From 27a578079080c37e3797233db86e4f72d8bf10d0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Vin=C3=ADcius=20Garcia?= Date: Thu, 19 Oct 2023 09:24:40 -0300 Subject: [PATCH] Updated Comparing KSQL with Other Tools (markdown) --- Comparing-KSQL-with-Other-Tools.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Comparing-KSQL-with-Other-Tools.md b/Comparing-KSQL-with-Other-Tools.md index 7858839..b18dc79 100644 --- a/Comparing-KSQL-with-Other-Tools.md +++ b/Comparing-KSQL-with-Other-Tools.md @@ -45,6 +45,8 @@ However, there are also reasons not to: 4. Sometimes the generated functions will not be as flexible as you need forcing you to make some tricks with SQL, that happens for example with `sqlc` for partial updates. +Finally it is important to note that contrary to most people's expectations the Benchmarks on the README file do not indicate sqlc or sqlboiler are any faster than KSQL, sqlx, pgx or the `database/sql` library. This also makes sense given the fact that the generated code also uses the `database/sql` library internally. + ## Some final notes All these tools work, and they all have trade-offs. I am not saying KSQL is the only good solution.