Results of 1 - 10 of about 103 for schema (0.002 sec.)
- DuckDB_% Metadata Functions 10327
- DuckDB offers a collection of table functions that provide metadata about the current database. These functions reside in the main schema and their names are prefixed with duckdb_ . The resultset returned by a duckdb_ table function may be
...ory. For some of the duckdb_% functions, there is also an identically named view available, which also resides in the main schema. Typically, these views do a SELECT on the duckdb_ table function with the same name, while filtering out those objects th...ntains the column object. VARCHAR database_oid Internal identifier of the database that contains the column object. BIGINT schema_name The SQL name of the schema that contains the table object that defines this column. VARCHAR schema_oid Internal ident...ifier of the schema object that contains the table of the column. BIGINT table_name The SQL name of the table that defines the column. VARCHAR... - https://man.mtool.work/duckdb/2.0/sql/meta/duckdb_table_functions.html
- Information Schema 10288
- The views in the information_schema are SQL-standard views that describe the catalog entries of the database. These views can be filtered to obtain information about a specific column or table. DuckDB's implementation is based on PostgreSQL
...'s information schema . Tables character_sets : Character Sets Column Description Type Example character_set_catalog Currently not implemented –...always NULL . VARCHAR NULL character_set_schema Currently not implemented – always NULL . VARCHAR NULL character_set_name Name of the character set, currently implemented...talog Name of the database containing the default collation (always the current database). VARCHAR 'my_db' default_collate_schema Name of the schema containing the default collation. VARCHAR 'pg_catalog' default_collate_name Name of the default collati... - https://man.mtool.work/duckdb/2.0/sql/meta/information_schema.html
- CREATE SCHEMA Statement 10095
- The CREATE SCHEMA statement creates a schema in the catalog. The default schema is main . Examples Create a schema: CREATE SCHEMA s1; Create a schema if it does not exist yet: CREATE SCHEMA IF NOT EXISTS s2; Create a schema or replace a schema
...ema if it exists: CREATE OR REPLACE SCHEMA s2; Create table in the schemas: CREATE TABLE s1.t (id INTEGER PRIMARY KEY, other_id INTEGER); CREATE TABLE s2.t (id INTEG...ER PRIMARY KEY, j VARCHAR); Compute a join between tables from two schemas: SELECT * FROM s1.t s1t, s2.t s2t WHERE s1t.other_id = s2t.id; Nested Schemas New Support for nested schemas was introduc...ed in DuckDB 2.0. Schemas can be nested within other schemas. Objects in a nested schema are referenced using their fully qualified, dot-separated... - https://man.mtool.work/duckdb/2.0/sql/statements/create_schema.html
- DROP Statement 9888
- The DROP statement removes a catalog entry added previously with the CREATE command. Examples Delete the table with the name tbl : DROP TABLE tbl; Drop the view with the name view1 ; do not throw an error if the view does not exist: DROP VI
...EW IF EXISTS view1; Drop function fn : DROP FUNCTION fn; Drop index idx : DROP INDEX idx; Drop schema sch : DROP SCHEMA sch; Drop sequence seq : DROP SEQUENCE seq; Drop macro mcr : DROP MACRO mcr; Drop macro table mt : DROP...t. If the CASCADE clause is provided then all the objects that are dependent on the object will be dropped as well. CREATE SCHEMA myschema; CREATE TABLE myschema.t1 (i INTEGER); DROP SCHEMA myschema; Dependency Error: Cannot drop entry "myschema" becau...se there are entries that depend on it. table "t1" depends on schema "myschema". Use DROP...CASCADE to drop all dependents. The CASCADE modifier drops both myschema and myschema.t1 : CREATE S... - https://man.mtool.work/duckdb/2.0/sql/statements/drop.html
- List Tables 9746
- The SHOW TABLES command can be used to obtain a list of all tables within the selected schema. CREATE TABLE tbl (i INTEGER); SHOW TABLES; name tbl SHOW or SHOW ALL TABLES can be used to obtain a list of all tables within all attached databa
...ses and schemas. CREATE TABLE tbl (i INTEGER); CREATE SCHEMA s1; CREATE TABLE s1.tbl (v VARCHAR); SHOW ALL TABLES; database schema name c...INTEGER] false memory s1 tbl [v] [VARCHAR] false SHOW TABLES FROM db can be used to list all tables in a given database or schema. ATTACH 'db.duckdb'; CREATE TABLE db.main_tbl (u VARCHAR); CREATE SCHEMA db.s1; CREATE TABLE db.s1.schema_tbl (v VARCHAR);...SHOW TABLES FROM db; name main_tbl schema_tbl Or a specific schema. SHOW TABLES FROM db.s1; name schema_tbl To view the schema of an individual table, use the DESCR... - https://man.mtool.work/duckdb/2.0/guides/meta/list_tables.html
- Iceberg Functions 9682
- The iceberg extension provides the following functions: Function Description iceberg_scan(source) Reads an Iceberg table from a path. iceberg_metadata(source) Returns the manifest entries of an Iceberg table. iceberg_snapshots(source) Retur
...ecified table. remove_iceberg_table_properties(table, property_names) Removes properties from the specified table. iceberg_schema_properties(schema) Returns all properties of the specified schema. set_iceberg_schema_properties(schema, properties) Sets...properties on the specified schema. remove_iceberg_schema_properties(schema, property_list) Removes properties from the specified schema. iceberg_rollback_to...e': 'merge-on-read' }); CALL remove_iceberg_table_properties( 'iceberg_catalog.default.my_table', ['write.update.mode'] ); Schema Properties Functions Iceberg catalogs allow arbitrary key-value properties to be attached at the schema (namespace) level.... - https://man.mtool.work/duckdb/2.0/core_extensions/iceberg/iceberg_functions.html
- ATTACH and DETACH Statements 9656
- DuckDB allows attaching to and detaching from database files. Examples Attach the database file.db with the alias inferred from the name ( file ): ATTACH 'file.db'; Attach the database file.db with an explicit alias ( file_db ): ATTACH 'fil
...atabase files. Attaching a database managed by another system accepts additional type-specific options, such as SECRET and SCHEMA . See the relevant extension page for the full list: PostgreSQL , MySQL , and Iceberg . Database Type The TYPE option spec...he duckdb module). DETACH Syntax Name Qualification The fully qualified name of catalog objects contains the catalog , the schema and the name of the object. For example: Attach the database new_db : ATTACH 'new_db.db'; Create the schema my_schema in t...he database new_db : CREATE SCHEMA new_db.my_schema; Create the table my_table in the schema my_schema : CREATE TABLE new_db.my_schema.my_table (col INTEGER)... - https://man.mtool.work/duckdb/2.0/sql/statements/attach.html
- Unity Catalog Extension 9307
- The unity_catalog extension attaches a Unity Catalog catalog, on Databricks or Unity Catalog OSS, as a DuckDB database. You can list, read, insert into and create its Delta Lake tables. It uses the delta extension to access the tables. For
...oken⟩', ENDPOINT '⟨endpoint⟩', AWS_REGION '⟨region⟩' ); ATTACH '⟨catalog_name⟩' AS my_catalog (TYPE unity_catalog, DEFAULT_SCHEMA 'main'); ENDPOINT is the Unity Catalog REST API endpoint. For Databricks, it is your Workspace URL , typically https://⟨in...secret . Note Only Databricks reports a default namespace. When you attach a Unity Catalog OSS catalog, always set DEFAULT_SCHEMA : without it, queries against the catalog fail, even with fully qualified table names. Attach Options When attaching a Uni...CHAR unnamed secret Name of the unity_catalog secret to use. Without it, the unnamed unity_catalog secret is used. DEFAULT_SCHEMA VARCHAR detected Schema that unqualified table names resolve to. Without it, DuckDB asks the server for the workspace's de... - https://man.mtool.work/duckdb/2.0/core_extensions/unity_catalog.html
- QUALIFY Clause 9243
- The QUALIFY clause is used to filter the results of WINDOW functions . This filtering of results is similar to how a HAVING clause filters the results of aggregate functions applied based on the GROUP BY clause . The QUALIFY clause avoids t
...g examples produce the same output, located below. Filter based on a window function defined in the QUALIFY clause: SELECT schema_name, function_name, -- In this example the function_rank column in the select clause is for reference row_number() OVER (...PARTITION BY schema_name ORDER BY function_name) AS function_rank FROM duckdb_functions() QUALIFY row_number() OVER (PARTITION BY schema_name...ORDER BY function_name) < 3; Filter based on a window function defined in the SELECT clause: SELECT schema_name, function_name, row_number() OVER (PARTITION BY schema_name ORDER BY function_name) AS function_rank FROM duckdb_func... - https://man.mtool.work/duckdb/2.0/sql/query_syntax/qualify.html
- USE Statement 8972
- The USE statement selects a database and optional schema, or just a schema to use as the default. Examples --- Sets the 'memory' database as the default. Will use 'main' schema implicitly or error --- if it does not exist. USE memory; --- S
...ets the 'duck.main' database and schema as the default USE duck.main; -- Sets the `main` schema of the currently selected database as the default, in this case 'd...uck.main' USE main; Syntax The USE statement sets a default database, schema or database/schema combination to use for future operations. For instance, tables created without providing a fully qualif... - https://man.mtool.work/duckdb/2.0/sql/statements/use.html
DuckDB 2.0 Documentation / man.mtool.work