Results of 1 - 10 of about 48 for view (0.003 sec.)
- CREATE VIEW Statement 14480
- The CREATE VIEW statement defines a new view in the catalog. Examples Create a simple view: CREATE VIEW view1 AS SELECT * FROM tbl; Create a view or replace it if a view with that name already exists: CREATE OR REPLACE VIEW view1 AS SELECT
...42; Create a view and replace the column names: CREATE VIEW view1 (a) AS SELECT 42; New The SECURE VIEW feature was introduced in DuckDB 2.0.... Create a secure view (hides internals from functions such as stats() and EXPLAIN ANALYZE ): CREATE SECURE VIEW users AS SELECT username FROM al...l_users WHERE access_level = 'standard'; The SQL query behind an existing view can be read using the duckdb_views() function like this: SELECT sql FROM duckdb_views() WHERE view_name = 'view1'; Syntax... - https://man.mtool.work/duckdb/2.0/sql/statements/create_view.html
- ALTER VIEW Statement 12268
- The ALTER VIEW statement changes the schema of an existing view in the catalog. Examples Rename a view: ALTER VIEW view1 RENAME TO view2; ALTER VIEW changes the schema of an existing view. All the changes made by ALTER VIEW fully respect th
...y will not be visible to other transactions until committed, and can be fully reverted through a rollback. Note that other views that rely on the view are not automatically updated.... - https://man.mtool.work/duckdb/2.0/sql/statements/alter_view.html
- Handle Results 10193
- Overview DuckDB is columnar, and beyond reading a result set row by row through database/sql , the Go client can exchange whole results with Apache Arrow as a stream of record batches, and register an Arrow stream as a queryable view. Both
...text() accepts bound parameters as trailing arguments, the same as database/sql queries . Registering an Arrow Stream as a View An Arrow stream produced elsewhere in a program, an array.RecordReader , can be registered as a DuckDB view and queried in...SQL. RegisterView() takes the reader and a view name, and returns a release function that unregisters the view; call it when the view is no...longer needed: release, err := ar.RegisterView(reader, "my_arrow_view") if err != nil { log.Fatal(err) } defer release() result, err := ar.QueryContext(context.Backgroun... - https://man.mtool.work/duckdb/2.0/clients/go/result_handling.html
- DROP Statement 9572
- 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 VIEW
...EW IF EXISTS view1; Drop function fn : DROP FUNCTION fn; Drop index idx : DROP INDEX idx; Drop schema sch : DROP SCHEMA sch; Drop sequence s...object type SCHEMA FUNCTION SCHEMA MACRO TABLE SCHEMA MACRO SCHEMA SCHEMA SCHEMA SEQUENCE SCHEMA TABLE SCHEMA TYPE SCHEMA VIEW Limitations Dependencies on Views Currently, dependencies are not tracked for views. For example, if a view is created tha...t references a table and the table is dropped, then the view will be in an invalid state: CREATE TABLE tbl (i INTEGER); CREATE VIEW view1 AS SELECT i FROM tbl; DROP TABLE tbl RESTRICT... - https://man.mtool.work/duckdb/2.0/sql/statements/drop.html
- DuckDB_% Metadata Functions 9481
- 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
...used just like an ordinary table or view. For example, you can use a duckdb_ function call in the FROM clause of a SELECT statement, and you may refer to the colum...); In this case too, the parentheses are mandatory. 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 th...lly omit the parentheses in your duckdb_ table function call, you might still get a result, but from the identically named view. Example: The duckdb_views() table function returns all views, including those marked internal: SELECT * FROM duckdb_views... - https://man.mtool.work/duckdb/2.0/sql/meta/duckdb_table_functions.html
- Information Schema 9254
- 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
...lation. VARCHAR 'pg_catalog' default_collate_name Name of the default collation. VARCHAR 'ucs_basic' columns : Columns The view that describes the catalog information for columns is information_schema.columns . It lists the columns present in the dat...ed and generation_expression columns were introduced in DuckDB 2.0. constraint_column_usage : Constraint Column Usage This view describes all columns in the current database that are used by some constraint. For a check constraint, this view identifi...es the columns that are used in the check expression. For a not-null constraint, this view identifies the column that the constraint is defined on. For a foreign key constraint, this view identifies the columns th... - https://man.mtool.work/duckdb/2.0/sql/meta/information_schema.html
- COMMENT ON Statement 9027
- The COMMENT ON statement allows adding metadata to catalog entries (tables, columns, etc.). It follows the PostgreSQL syntax . Examples Create a comment on a TABLE : COMMENT ON TABLE test_table IS 'very nice table'; Create a comment on a CO
...LUMN : COMMENT ON COLUMN test_table.test_table_column IS 'very nice column'; Create a comment on a VIEW : COMMENT ON VIEW test_view IS 'very nice view'; Create a comment on an INDEX : COMMENT ON INDEX test_index IS 'very nice...s: SELECT comment FROM duckdb_tables(); List comments on COLUMN s: SELECT comment FROM duckdb_columns(); List comments on VIEW s: SELECT comment FROM duckdb_views(); List comments on INDEX s: SELECT comment FROM duckdb_indexes(); List comments on SE... - https://man.mtool.work/duckdb/2.0/sql/statements/comment_on.html
- Share a DuckDB Database That Only Stores Views 8800
- A DuckDB database file does not have to contain any data: it can store only view definitions that point at remote data such as Parquet files on object storage. The resulting file is only a few hundred kilobytes, yet it behaves like a shared
...in its original location and format. This is useful for publishing a curated “semantic layer” over a data lake, where the view definitions encode the joins, filters, and column names that consumers should use, without copying or moving the data itse...TALL httpfs SQL command. This only needs to be run once. Building the Catalog Create a persistent database file and define views that reference the remote data. Use fully qualified locations (remote URLs or absolute paths) so that the views resolve r...egardless of the client's working directory: ATTACH 'catalog.duckdb' AS catalog; USE catalog; CREATE VIEW services AS SELECT * FROM read_parquet('s3://my-bucket/rail/services/*.parquet'); CREATE VIEW stations AS SELECT * FROM re... - https://man.mtool.work/duckdb/2.0/guides/network_cloud_storage/duckdb_views_only...
- Python Client API 8163
- 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
...PyRelation Create a relation object from the Parquet path(s) or file-like object(s) in ‘path_or_buffer'. register ( self , view_name : str , python_object : object ) → _duckdb.DuckDBPyConnection Register the passed Python Object value for querying wi...th a view register_filesystem ( self , filesystem : object | None ) → None Register a fsspec compliant filesystem remove_function (...( self , members : object ) → _duckdb._sqltypes.DuckDBPyType Create a union type object from ‘members' unregister ( self , view_name : str ) → _duckdb.DuckDBPyConnection Unregister the view name unregister_filesystem ( self , name : str ) → None Unre... - https://man.mtool.work/duckdb/2.0/clients/python/reference/
- Iceberg Functions 8163
- 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
...of an Iceberg table. iceberg_scan_plan(table) Returns the scan tasks (files to read) planned for an Iceberg table. iceberg_view_metadata(view) Returns the raw LoadView response of the REST Catalog. iceberg_table_properties(table) Returns all properti...ke.default.t AT (TIMESTAMP => TIMESTAMP '2025-09-22 12:32:43.217') Table Properties Functions DuckDB provides functions to view and modify Iceberg table properties : Function Description iceberg_table_properties(table) Returns all properties of the s...es from the specified table. You can also use ALTER TABLE ... SET and ALTER TABLE ... RESET to modify table properties: -- View table properties SELECT * FROM iceberg_table_properties(iceberg_catalog.default.my_table); -- Set table properties ALTER T... - https://man.mtool.work/duckdb/2.0/core_extensions/iceberg/iceberg_functions.html
DuckDB 2.0 Documentation / man.mtool.work