- Installation
- Documentation
- Getting Started
- Connect
- Data Import
- Overview
- Data Sources
- CSV Files
- JSON Files
- Overview
- Creating JSON
- Loading JSON
- Writing JSON
- JSON Type
- JSON Functions
- Format Settings
- Installing and Loading
- SQL to / from JSON
- Caveats
- Multiple Files
- Parquet Files
- Partitioning
- Appender
- INSERT Statements
- Client APIs
- Overview
- C
- Overview
- Startup
- Configuration
- Query
- Data Chunks
- Vectors
- Values
- Types
- Prepared Statements
- Appender
- Table Functions
- Replacement Scans
- API Reference
- C++
- CLI
- Dart
- Go
- Java
- Julia
- Node.js
- Python
- Overview
- Data Ingestion
- Conversion between DuckDB and Python
- DB API
- Relational API
- Function API
- Types API
- Expression API
- Spark API
- API Reference
- Known Python Issues
- R
- Rust
- Swift
- Wasm
- ADBC
- ODBC
- SQL
- Introduction
- Statements
- Overview
- ANALYZE
- ALTER TABLE
- ALTER VIEW
- ATTACH and DETACH
- CALL
- CHECKPOINT
- COMMENT ON
- COPY
- CREATE INDEX
- CREATE MACRO
- CREATE SCHEMA
- CREATE SECRET
- CREATE SEQUENCE
- CREATE TABLE
- CREATE VIEW
- CREATE TYPE
- DELETE
- DESCRIBE
- DROP
- EXPORT and IMPORT DATABASE
- INSERT
- PIVOT
- Profiling
- SELECT
- SET / RESET
- SET VARIABLE
- SUMMARIZE
- Transaction Management
- UNPIVOT
- UPDATE
- USE
- VACUUM
- LOAD / INSTALL
- Query Syntax
- SELECT
- FROM and JOIN
- WHERE
- GROUP BY
- GROUPING SETS
- HAVING
- ORDER BY
- LIMIT and OFFSET
- SAMPLE
- Unnesting
- WITH
- WINDOW
- QUALIFY
- VALUES
- FILTER
- Set Operations
- Prepared Statements
- Data Types
- Overview
- Array
- Bitstring
- Blob
- Boolean
- Date
- Enum
- Interval
- List
- Literal Types
- Map
- NULL Values
- Numeric
- Struct
- Text
- Time
- Timestamp
- Time Zones
- Union
- Typecasting
- Expressions
- Overview
- CASE Statement
- Casting
- Collations
- Comparisons
- IN Operator
- Logical Operators
- Star Expression
- Subqueries
- Functions
- Overview
- Aggregate Functions
- Array Functions
- Bitstring Functions
- Blob Functions
- Date Format Functions
- Date Functions
- Date Part Functions
- Enum Functions
- Interval Functions
- Lambda Functions
- List Functions
- Map Functions
- Nested Functions
- Numeric Functions
- Pattern Matching
- Regular Expressions
- Struct Functions
- Text Functions
- Time Functions
- Timestamp Functions
- Timestamp with Time Zone Functions
- Union Functions
- Utility Functions
- Window Functions
- Constraints
- Indexes
- Meta Queries
- DuckDB's SQL Dialect
- Samples
- Configuration
- Extensions
- Overview
- Core Extensions
- Community Extensions
- Working with Extensions
- Versioning of Extensions
- Arrow
- AutoComplete
- AWS
- Azure
- Delta
- Excel
- Full Text Search
- httpfs (HTTP and S3)
- Iceberg
- ICU
- inet
- jemalloc
- MySQL
- PostgreSQL
- Spatial
- SQLite
- Substrait
- TPC-DS
- TPC-H
- VSS
- Guides
- Overview
- Data Viewers
- Database Integration
- File Formats
- Overview
- CSV Import
- CSV Export
- Directly Reading Files
- Excel Import
- Excel Export
- JSON Import
- JSON Export
- Parquet Import
- Parquet Export
- Querying Parquet Files
- Network and Cloud Storage
- Overview
- HTTP Parquet Import
- S3 Parquet Import
- S3 Parquet Export
- S3 Iceberg Import
- S3 Express One
- GCS Import
- Cloudflare R2 Import
- DuckDB over HTTPS / S3
- Meta Queries
- Describe Table
- EXPLAIN: Inspect Query Plans
- EXPLAIN ANALYZE: Profile Queries
- List Tables
- Summarize
- DuckDB Environment
- ODBC
- Performance
- Overview
- Environment
- Import
- Schema
- Indexing
- Join Operations
- File Formats
- How to Tune Workloads
- My Workload Is Slow
- Benchmarks
- Python
- Installation
- Executing SQL
- Jupyter Notebooks
- SQL on Pandas
- Import from Pandas
- Export to Pandas
- Import from Numpy
- Export to Numpy
- SQL on Arrow
- Import from Arrow
- Export to Arrow
- Relational API on Pandas
- Multiple Python Threads
- Integration with Ibis
- Integration with Polars
- Using fsspec Filesystems
- SQL Editors
- SQL Features
- Snippets
- Glossary of Terms
- Browse Offline
- Operations Manual
- Overview
- Limits
- Non-Deterministic Behavior
- Embedding DuckDB
- DuckDB's Footprint
- Securing DuckDB
- Development
- DuckDB Repositories
- Testing
- Overview
- sqllogictest Introduction
- Writing Tests
- Debugging
- Result Verification
- Persistent Testing
- Loops
- Multiple Connections
- Catch
- Profiling
- Release Calendar
- Building
- Benchmark Suite
- Internals
- Sitemap
- Why DuckDB
- Media
- FAQ
- Code of Conduct
- Live Demo
Typecasting is an operation that converts a value in one particular data type to the closest corresponding value in another data type. Like other SQL engines, DuckDB supports both implicit and explicit typecasting.
Explicit Casting
Explicit typecasting is performed by using a CAST
expression. For example, CAST(col AS VARCHAR)
or col::VARCHAR
explicitly cast the column col
to VARCHAR
. See the cast page for more information.
Implicit Casting
In many situations, the system will add casts by itself. This is called implicit casting. This happens for example when a function is called with an argument that does not match the type of the function, but can be casted to the desired type.
Consider the function sin(DOUBLE)
. This function takes as input argument a column of type DOUBLE
, however, it can be called with an integer as well: sin(1)
. The integer is converted into a double before being passed to the sin
function.
Implicit casts can only be added for a number of type combinations, and is generally only possible when the cast cannot fail. For example, an implicit cast can be added from INTEGER
to DOUBLE
– but not from DOUBLE
to INTEGER
.
Casting Operations Matrix
Values of a particular data type cannot always be cast to any arbitrary target data type. The only exception is the NULL
value – which can always be converted between types.
The following matrix describes which conversions are supported.
When implicit casting is allowed, it implies that explicit casting is also possible.
Even though a casting operation is supported based on the source and target data type, it does not necessarily mean the cast operation will succeed at runtime.
Deprecated Prior to version 0.10.0, DuckDB allowed any type to be implicitly cast to
VARCHAR
during function binding. Version 0.10.0 introduced a breaking change which no longer allows implicit casts toVARCHAR
. Theold_implicit_casting
configuration option setting can be used to revert to the old behavior. However, please note that this flag will be deprecated in the future.
Lossy Casts
Casting operations that result in loss of precision are allowed. For example, it is possible to explicitly cast a numeric type with fractional digits like DECIMAL
, FLOAT
or DOUBLE
to an integral type like INTEGER
. The number will be rounded.
SELECT CAST(3.5 AS INTEGER);
Overflows
Casting operations that would result in a value overflow throw an error. For example, the value 999
is too large to be represented by the TINYINT
data type. Therefore, an attempt to cast that value to that type results in a runtime error:
SELECT CAST(999 AS TINYINT);
Conversion Error: Type INT32 with value 999 can't be cast because the value is out of range for the destination type INT8
So even though the cast operation from INTEGER
to TINYINT
is supported, it is not possible for this particular value. TRY_CAST can be used to convert the value into NULL
instead of throwing an error.
Varchar
The VARCHAR
type acts as a univeral target: any arbitrary value of any arbitrary type can always be cast to the VARCHAR
type. This type is also used for displaying values in the shell.
SELECT CAST(42.5 AS VARCHAR);
Casting from VARCHAR
to another data type is supported, but can raise an error at runtime if DuckDB cannot parse and convert the provided text to the target data type.
SELECT CAST('NotANumber' AS INTEGER);
In general, casting to VARCHAR
is a lossless operation and any type can be cast back to the original type after being converted into text.
SELECT CAST(CAST([1, 2, 3] AS VARCHAR) AS INTEGER[]);
Literal Types
Integer literals (such as 42
) and string literals (such as 'string'
) have special implicit casting rules. See the literal types page for more information.
Lists / Arrays
Lists can be explicitly cast to other lists using the same casting rules. The cast is applied to the children of the list. For example, if we convert a INTEGER[]
list to a VARCHAR[]
list, the child INTEGER
elements are individually cast to VARCHAR
and a new list is constructed.
SELECT CAST([1, 2, 3] AS VARCHAR[]);
Arrays
Arrays follow the same casting rules as lists. In addition, arrays can be implicitly cast to lists of the same type. For example, an INTEGER[3]
array can be implicitly cast to an INTEGER[]
list.
Structs
Structs can be cast to other structs as long as the names of the child elements match.
SELECT CAST({'a': 42} AS STRUCT(a VARCHAR));
The names of the struct can also be in a different order. The fields of the struct will be reshuffled based on the names of the structs.
SELECT CAST({'a': 42, 'b': 84} AS STRUCT(b VARCHAR, a VARCHAR));
Unions
Union casting rules can be found on the UNION type page
.