From b391212352652ada055ffdae4b41d8a890f041e6 Mon Sep 17 00:00:00 2001 From: Florian Date: Tue, 22 Oct 2024 16:44:31 +0200 Subject: [PATCH] Remove mention of outdated MotherDuck constraints --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index 0f910e75..7468314a 100644 --- a/README.md +++ b/README.md @@ -51,9 +51,8 @@ or the Python API. MotherDuck databases generally work the same way as local DuckDB databases from the perspective of dbt, but there are a [few differences to be aware of](https://motherduck.com/docs/architecture-and-capabilities#considerations-and-limitations): -1. Currently, MotherDuck _requires_ a specific version of DuckDB, often the latest, as specified in [MotherDuck's documentation](https://motherduck.com/docs/intro/#getting-started) +1. MotherDuck is compatible with client DuckDB versions 0.10.2 and older. 1. MotherDuck preloads a set of the most common DuckDB extensions for you, but does not support loading custom extensions or user-defined functions. -1. A small subset of advanced SQL features are currently unsupported; the only impact of this on the dbt adapter is that the [dbt.listagg](https://docs.getdbt.com/reference/dbt-jinja-functions/cross-database-macros#listagg) macro and foreign-key constraints will work against a local DuckDB database, but will not work against a MotherDuck database. #### DuckDB Extensions, Settings, and Filesystems