Results of 1 - 2 of about 2 for salary (0.001 sec.)
- MERGE INTO Statement 11228
- 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
...have a primary key constraint. Examples First, let's create a simple table. CREATE TABLE people (id INTEGER, name VARCHAR, salary FLOAT); INSERT INTO people VALUES (1, 'John', 92_000.0), (2, 'Anna', 100_000.0); The simplest upsert would be to use a who...MERGE INTO people 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; i...d name salary 1 John 105000.0 2 Anna 100000.0 3 Sarah 95000.0 In the previous example we are updating the whole row if id matches. Howev... - https://man.mtool.work/duckdb/2.0/sql/statements/merge_into.html
- Writing to Iceberg 7485
- 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.
...iceberg_catalog.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 MAT... - https://man.mtool.work/duckdb/2.0/core_extensions/iceberg/writing_to_iceberg.htm...
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work