4 ms·

Adding to this. https://duckdb.org/2024/01/26/multi-database-support-in-duckdb.html https://duckdb.org/2024/01/26/multi-database-support-in-duck... Unsure wha

Adding to this. https://duckdb.org/2024/01/26/multi-database-support-in-duckdb.html https://duckdb.org/2024/01/26/multi-database-support-in-duck... Unsure what the parent means by "ingest" SQLite tables (although i believe you can use COPY with sqlite tables in DuckDB), but you can interact with sqlite tables in DuckDB using the extension to attach to a sqlite db. https://duckdb.org/docs/extensions/sqlite https://duckdb.org/docs/extensions/sqlite

jitl 3y ago
Yeah by ingest I mean COPY FROM or attach via the SQLite extension. Then you can `INSERT INTO duckdbTable (select * from sqliteDb.sqliteTable)` or similar. I don’t think duckdb aggregate on native SQLite format will have any advantage; I think the native duckdb format would be necessary to see a big advantage over doing the aggregate in SQLite directly based on my reading of the duckdb extension code.
- hantusk 3y ago
  That's not true for postgres scanning: https://duckdb.org/2022/09/30/postgres-scanner.html https://duckdb.org/2022/09/30/postgres-scanner.html So i would think we'd see similar speedups for sqlite even without copying any data