Using the package from R: connect, query, and configure DuckDB. The SQL dialect, the storage format, and the engine's own tuning are DuckDB's to document; a leaf here is worth writing where the two sides meet — where R's idea of a type, a lifetime, or a file location has to be reconciled with the engine's.
The package decides as little as it can, and says so when it must. A default that commits the user to something — a location on disk, a download, a silent conversion — is announced, reversible, or refused outright, never taken quietly; the leaves say which of the three. Making the choice explicit is the interface, and is what turns the announcement off.
installation/— CRAN, r-universe, and the flavorsconnections/—dbConnect(), instances, shutdownstatements/— queries, transactions, tables, quotingtypes/— the R ↔ DuckDB type mappingtimestamps/— timestamps, time zones, and their labelsextensions/— what ships, what installsmemory/— limits, spill, streamingdata-import/— CSV and Parquet ingestionstorage/— where extensions and secrets liveintegrations/— dbplyr, duckplyr, and Arrowrelational/— the internal lazy-relation APIinteractive/— what a session does while you work