Results of 1 - 5 of about 5 for upserts (0.003 sec.)
- MERGE INTO Statement 12225
- The MERGE INTO statement is an alternative to INSERT INTO ... ON CONFLICT that doesn't need a primary key since it allows for a custom match condition. This is a very useful alternative for upserting use cases ( INSERT + UPDATE ) when the d
...eople USING ( SELECT unnest([3, 1]) AS id, unnest(['Sarah', 'John']) AS name, unnest([95_000.0, 105_000.0]) AS salary ) AS upserts ON (upserts.id = people.id) WHEN MATCHED THEN UPDATE WHEN NOT MATCHED THEN INSERT; FROM people ORDER BY id; id name salary...(1, 'John', 105_000.0); MERGE INTO people USING ( SELECT unnest([3, 1]) AS id, unnest([89_000.0, 70_000.0]) AS salary ) AS upserts USING (id) WHEN MATCHED AND people.salary < 100_000.0 THEN UPDATE SET salary = upserts.salary -- Second update or delete c... - https://man.mtool.work/duckdb/2.0/sql/statements/merge_into.html
- Writing to Iceberg 10387
- The DuckDB iceberg extension supports writing to Iceberg tables when an Iceberg catalog is attached. Writing to a table read directly from storage with iceberg_scan is not supported: the catalog is required to commit the new table metadata.
...nal deletes, see Limitations for UPDATE and DELETE . MERGE INTO The MERGE INTO statement is the recommended way to express upserts against Iceberg tables, which do not have a primary key. You can apply a change set in a single statement, deciding per ro...og.default.people AS target USING ( FROM (VALUES (1, 'John', 105_000.0), (3, 'Sarah', 95_000.0) ) t(id, name, salary) ) AS upserts ON (upserts.id = target.id) WHEN MATCHED THEN UPDATE WHEN NOT MATCHED THEN INSERT; You can also use WHEN MATCHED THEN DELE... - https://man.mtool.work/duckdb/2.0/core_extensions/iceberg/writing_to_iceberg.htm...
- Appender 8015
- Use an appender to insert rows that your Python code produces. It collects rows and writes them together in one SQL statement; this is called flushing. The with block below flushes on successful exit: import duckdb con = duckdb.connect() co
....appender("events", columns=["kind"]) appender.append_row("login") appender.append_row("logout") appender.flush() Updates, Upserts and Deletes The action argument picks the statement: "insert" (the default), "upsert" , "update" or "delete" . An upsert i... - https://man.mtool.work/duckdb/2.0/clients/python/appender.html
- Merge Statement for SCD Type 2 7831
- This is a practical, step-by-step guide to using DuckDB's MERGE statement (introduced in v1.4.0) to perform upserts and build Slowly Changing Dimension Type 2 (SCD Type 2) tables . Type 2 SCDs let you keep full historical versions of record
... - https://man.mtool.work/duckdb/2.0/guides/sql_features/merge.html
- Python Client API 7464
- Connection class duckdb. Appender Bases: object append_row ( self , * args ) → None Buffer one row, one value per column, each converted as an executemany parameter would be append_rows ( self , rows : object ) → None Buffer each row of an
...action : str = 'insert' , key : list | None = None ) → _duckdb.Appender Create an appender that buffers rows and inserts, upserts, updates or deletes them in the named table at each flush array_type ( self , type : _duckdb._sqltypes.DuckDBPyType , size...nnection : _duckdb.DuckDBPyConnection | None = None ) → _duckdb.Appender Create an appender that buffers rows and inserts, upserts, updates or deletes them in the named table at each flush duckdb. arrow ( arrow_object : object , * , connection : DuckDBP... - https://man.mtool.work/duckdb/2.0/clients/python/reference/
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work