Results of 1 - 10 of about 36 for error message (0.005 sec.)
error (163), message (42)
- Complete API 22031
- This page contains the reference for DuckDB's C API. The reference contains several deprecation notices. These concern methods whose long-term availability is not guaranteed as they may be removed in the future. That said, DuckDB's develope
...db_instance_cache instance_cache , const char * path , duckdb_database * out_database , duckdb_config config , char ** out_error ); void duckdb_destroy_instance_cache ( duckdb_instance_cache * instance_cache ); duckdb_state duckdb_open ( const char *...); duckdb_state duckdb_open_ext ( const char * path , duckdb_database * out_database , duckdb_config config , char ** out_error ); void duckdb_close ( duckdb_database * database ); duckdb_state duckdb_connect ( duckdb_database database , duckdb_conne...( duckdb_config * config ); Error Data duckdb_error_data duckdb_create_error_data ( duckdb_error_type type , const char * message ); void duckdb_destroy_error_data ( duckdb_error_data * error_data ); duckdb_error_type duckdb_error_data_error_type ( duc... - https://man.mtool.work/duckdb/2.0/clients/c/api.html
- Reading Faulty CSV Files 19440
- CSV files can come in all shapes and forms, with some presenting many errors that make the process of cleanly reading them inherently difficult. To help users read these files, DuckDB supports detailed error messages, the ability to skip fa
...nes and the possibility of storing faulty lines in a temporary table to assist users with a data cleaning step. Structural Errors DuckDB supports the detection and skipping of several different structural errors. In this section, we will go over each...examples, consider the following table: CREATE TABLE people (name VARCHAR, birth_date DATE); DuckDB detects the following error types: CAST : Casting errors occur when a column in the CSV file cannot be cast to the expected schema value. For example,...ch information as possible to allow users to evaluate them directly in their CSV file. This is an example for a full error message: Conversion Error: CSV Error on Line: 5648 Original Line: Pedro,The 90s Error when converting column "birth_date". date fi... - https://man.mtool.work/duckdb/2.0/data/csv/reading_faulty_csv_files.html
- Result Verification 18347
- The standard way of verifying results of queries is using the query statement, followed by the letter I times the number of columns that are expected in the result. After the query, four dashes ( ---- ) are expected followed by the result v
...d use the string NULL , and empty strings should use the string (empty) , e.g.: query II SELECT NULL, '' ---- NULL (empty) Error Verification In order to signify that an error is expected, the statement error indicator can be used. The statement error...also takes an optional expected result – which is interpreted as the expected error message . Similar to query , the expected error should be placed after the four dashes ( ---- ) following the query. The t...est passes if the error message contains the text under statement error – the entire error message does not need to be provided. It is recommended that yo... - https://man.mtool.work/duckdb/2.0/dev/sqllogictest/result_verification.html
- Appender 18127
- Appenders are the most efficient way of loading data into DuckDB from within the C interface, and are recommended for fast data loading. The appender is much faster than using prepared statements or individual INSERT INTO statements. Append
...y. Note that duckdb_appender_destroy should always be called on the resulting appender, even if the function returns DuckDBError . Example duckdb_query(con, "CREATE TABLE people (id INTEGER, name VARCHAR)", NULL); duckdb_appender appender; if (duckdb_...appender_create(con, NULL, "people", &appender) == DuckDBError) { // handle error } // append the first row (1, Mark) duckdb_append_int32(appender, 1); duckdb_append_varchar(appender, "...otice. This method is scheduled for removal in a future release. Use duckdb_appender_error_data instead. Returns the error message associated with the appender. If the appender has no error message, this returns nullptr instead. The error message should... - https://man.mtool.work/duckdb/2.0/clients/c/appender.html
- Troubleshooting 18035
- Curl Request Fails Problem When trying to attach to an Iceberg REST Catalog endpoint, DuckDB returns the following error: IO Error: Curl Request to '/v1/oauth/tokens' failed with error: 'URL using bad/illegal format or missing URL' Solution
...installed: duckdb FORCE INSTALL iceberg FROM core_nightly; Exit DuckDB and start a new session: duckdb LOAD iceberg; HTTP Error 403 Problem When trying to list the tables in a remote-attached catalog, DuckDB returns the following error: SHOW ALL TABL...ES; Failed to query https://s3tables.us-east-2.amazonaws.com/iceberg/v1/arn:aws:s3tables:... http error 403 thrown. Message: {"message":"The security token included in the request is invalid."} Solution Use the duckdb_secrets(... - https://man.mtool.work/duckdb/2.0/core_extensions/iceberg/troubleshooting.html
- Logging 16816
- DuckDB implements a logging mechanism that provides users with detailed information about events such as query execution, performance metrics and system events. Warning Logs may contain sensitive information, including secrets and credentia
...queries... SELECT * FROM duckdb_logs; In the CLI client , the default log storage is shell_log_storage , which prints log messages to the console but does not support querying. Therefore, the example above passes storage = 'memory' . In other clients,...logs(); Log Level DuckDB supports different logging levels that control the verbosity of the logs: FATAL : Only logs fatal errors ERROR : Logs error messages WARNING : Logs warnings and errors INFO : Logs general information, warnings and errors (defa...ALL enable_logging(level = 'warning', storage = 'memory'); -- Run some queries that may emit warnings... SELECT timestamp, message FROM duckdb_logs WHERE log_level = 'WARNING'; The default log level is INFO , which already includes warnings, so calling... - https://man.mtool.work/duckdb/2.0/operations_manual/logging/overview.html
- Prepared Statements 16786
- A prepared statement is a parameterized query. The query is prepared with question marks ( ? ) or dollar symbols ( $1 ) indicating the parameters of the query. Values can then be bound to these parameters, after which the prepared statement
...ared_statement stmt; duckdb_result result; if (duckdb_prepare(con, "INSERT INTO integers VALUES ($1, $2)", &stmt) == DuckDBError) { // handle error } duckdb_bind_int32(stmt, 1, 42); // the parameter index starts counting at 1! duckdb_bind_int32(stmt,...query result sets using prepared statements if (duckdb_prepare(con, "SELECT * FROM integers WHERE i = ?", &stmt) == DuckDBError) { // handle error } duckdb_bind_int32(stmt, 1, 42); duckdb_execute_prepared(stmt, &result); // do something with result /...red_statement ); Parameters prepared_statement : The prepared statement to destroy. duckdb_prepare_error Returns the error message associated with the given prepared statement. If the prepared statement has no error message, this returns nullptr instead... - https://man.mtool.work/duckdb/2.0/clients/c/prepared.html
- Startup & Shutdown 16546
- To use DuckDB, you must first initialize a duckdb_database handle using duckdb_open() . duckdb_open() takes as parameter the database file to read and write from. The special value NULL ( nullptr ) can be used to create an in-memory databas
...oid memory and file handle leaking. Example duckdb_database db; duckdb_connection con; if (duckdb_open(NULL, &db) == DuckDBError) { // handle error } if (duckdb_connect(db, &con) == DuckDBError) { // handle error } // run queries... // cleanup duckdb_...db_instance_cache instance_cache , const char * path , duckdb_database * out_database , duckdb_config config , char ** out_error ); void duckdb_destroy_instance_cache ( duckdb_instance_cache * instance_cache ); duckdb_state duckdb_open ( const char *...nfiguration used to create the database. out_error : If set and the function returns DuckDBError , this contains the error message. Note that the error message must be freed using duckdb_free . Return Value DuckDBSuccess on success or DuckDBError on fai... - https://man.mtool.work/duckdb/2.0/clients/c/connect.html
- Table Functions 16331
- The table function API can be used to define a table function that can then be called from within DuckDB in the FROM clause of a query. API Reference Overview duckdb_table_function duckdb_create_table_function (); void duckdb_destroy_table_
...oy ); void duckdb_bind_set_cardinality ( duckdb_bind_info info , idx_t cardinality , bool is_exact ); void duckdb_bind_set_error ( duckdb_bind_info info , const char * error ); Table Function Init void * duckdb_init_get_extra_info ( duckdb_init_info i...idx_t column_index ); void duckdb_init_set_max_threads ( duckdb_init_info info , idx_t max_threads ); void duckdb_init_set_error ( duckdb_init_info info , const char * error ); Table Function void * duckdb_function_get_extra_info ( duckdb_function_inf...duckdb_bind_set_error ( duckdb_bind_info info , const char * error ); Parameters info : The info object error : The error message duckdb_init_get_extra_info Retrieves the extra info of the function as set in duckdb_table_function_set_extra_info . Synta... - https://man.mtool.work/duckdb/2.0/clients/c/table_functions.html
- Internal Errors 16278
- Internal errors signal an assertion failure within DuckDB. They usually occur due to unexpected conditions or errors in the program's logic. For example, running issue 17002 on DuckDB 1.2.1 results in an internal error. INTERNAL Error: Atte
...cess index 3 within vector of size 3 The issue is fixed in DuckDB 1.2.2 and newer versions. After encountering an internal error, DuckDB enters “restricted mode”, where any further operations will result in the following error message: FATAL Error: Fa...iled: database has been invalidated because of a previous fatal error. The database must be restarted prior to being used again. To continue working with the same database, start a new DuckDB... - https://man.mtool.work/duckdb/2.0/dev/internal_errors.html
DuckDB 2.0 Documentation / man.mtool.work