From aec7f729216da7e103280be9e3206c62173f76e3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Vin=C3=ADcius=20Garcia?= Date: Sat, 15 Jul 2023 21:35:23 -0300 Subject: [PATCH] Updated Home (markdown) --- Home.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Home.md b/Home.md index 7d42dbe..ab52f3c 100644 --- a/Home.md +++ b/Home.md @@ -43,10 +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 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. +> Note: different backend drivers (e.g. one for Postgres, another for Mysql), +> might expect different SQL dialects and/or support different input types. +> KSQL only forwards the query, params and scan values to these drivers, and +> makes no attempt at hiding these differences. Currently, we already support the following databases: