From 016ca3310870a3b5e0ecbd6fa116d483a4adf873 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Vin=C3=ADcius=20Garcia?= Date: Sat, 15 Jul 2023 21:31:29 -0300 Subject: [PATCH] Updated Home (markdown) --- Home.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/Home.md b/Home.md index b8cf9eb..7d42dbe 100644 --- a/Home.md +++ b/Home.md @@ -43,9 +43,10 @@ Some special use-cases also have some special support: KSQL is well decoupled from its backend implementation which makes it easy to change the actual technology used. -> Note however that KSQL does not attempt to allow your code -> to work with multiple underlying databases with no changes -> on your SQL queries, you still need to use the repository pattern. +> Note however that different backend drivers for different databases +> will expect slightly different SQL dialects and also support different features. +> KSQL does not try to normalize this behavior, we just +> forward the query and params to the backend driver. Currently, we already support the following databases: