⌘K ctrl+k
Search Shortcut cmd + k | ctrl + k
DuckDB 2.0 ドキュメント 全文検索
per page, with , order by , clip by
Results of 1 - 10 of about 21 for Importing (0.001 sec.)
Excel Import 12820
DuckDB supports reading Excel .xlsx files. However, .xls files are not supported. Importing Excel Sheets Use the read_xlsx function in the FROM clause of a query: SELECT * FROM read_xlsx('test_excel.xlsx'); Alternatively, you can omit the r ... ECT * FROM read_xlsx('test_excel.xlsx', sheet = 'Sheet1'); By default, the first sheet is loaded if no sheet is specified. Importing a Specific Range To select a specific range of cells, use the range parameter with a string in the format A1:B2 , where A1 ... ting table, the types of the columns in the target table will be used to coerce the types of the cells in the Excel sheet. Importing a Sheet with/without a Header To treat the first row as containing the names of the resulting columns, use the header para ... nferred or supplied range) are non-empty strings. To disable this behavior, set header to false . Detecting Types When not importing into an existing table, DuckDB will attempt to infer the types of the columns in the Excel sheet based on their contents a ...
https://man.mtool.work/duckdb/2.0/guides/file_formats/excel_import.html
Data Import 12143
Recommended Import Methods When importing data from other systems to DuckDB, there are several considerations to take into account. We recommend importing using the following order: For systems which are supported by a DuckDB scanner extens ...
https://man.mtool.work/duckdb/2.0/guides/performance/import.html
EXPORT and IMPORT DATABASE Statements 10553
The EXPORT DATABASE command allows you to export the contents of the database to a specific directory. The IMPORT DATABASE command allows you to then read the contents again. Examples Export the database to the target directory target_direc ... riggers are not included in the export, and COPY FROM DATABASE does not copy them either. Recreate triggers manually after importing or copying a database. The load.sql file contains a set of COPY statements that can be used to read the data from the CSV ... xpects to import into a fresh database. schema.sql uses plain CREATE statements (without OR REPLACE or IF NOT EXISTS ), so importing into a database that already contains any of the exported objects – for example a user-defined type – fails with a "alread ...
https://man.mtool.work/duckdb/2.0/sql/statements/export.html
Export to Pandas 10097
The result of a query can be converted to a Pandas DataFrame using the df() function. import duckdb # read the result of an arbitrary SQL query to a Pandas DataFrame results = duckdb.sql("SELECT 42").df() results 42 0 42 See Also DuckDB als ... o supports importing from Pandas . ...
https://man.mtool.work/duckdb/2.0/guides/python/export_pandas.html
Troubleshooting 9420
Troubleshooting Running EXPLAIN Renders Newlines In Python, the output of the EXPLAIN statement contains hard line breaks ( \n ): In [1]: import duckdb ...: duckdb.sql("EXPLAIN SELECT 42 AS x") Out[1]: ┌───────────────┬───────────────────── ... othing. Please also check out the Jupyter guide for tips on using Jupyter with JupySQL. Crashes and Errors on Windows When importing DuckDB on Windows, the Python runtime may crash or return an error upon import or first use: import duckdb duckdb.sql("... ... ") ImportError: DLL load failed while importing duckdb: The specified module could not be found. Windows fatal exception: access violation Current thread 0x0000311c (most ...
https://man.mtool.work/duckdb/2.0/clients/python/known_issues.html
Export to Numpy 9420
The result of a query can be converted to Numpy arrays using the fetchnumpy() function, which returns a dictionary that maps each column name to a Numpy array. For example: import duckdb import numpy as np my_arr = duckdb.sql("SELECT unnest ... hen, the array can be processed using Numpy functions, e.g.: np.sum(my_arr['x']) np.int64(6) See Also DuckDB also supports importing from Numpy . ...
https://man.mtool.work/duckdb/2.0/guides/python/export_numpy.html
Enum Data Type 8981
Name Description ENUM Dictionary representing all possible string values of a column The enum type represents a dictionary data structure with all possible unique values of a column. For example, a column storing the days of the week can be ... ted automatically, and NULL values will be ignored: CREATE TYPE region AS ENUM (SELECT region FROM sales_data); If you are importing data from a file, you can create an enum for a VARCHAR column before importing: CREATE TYPE region AS ENUM (SELECT region ...
https://man.mtool.work/duckdb/2.0/sql/data_types/enum.html
GDAL Integration 8304
The spatial extension integrates the GDAL translator library to read and write spatial data from a variety of geospatial vector file formats. See the documentation for the st_read table function for how to make use of this in practice. In o ... to inspect which GDAL drivers are currently available. GDAL Based COPY Function The spatial extension does not only enable importing geospatial file formats (through the ST_Read function), it also enables exporting DuckDB tables to different geospatial ve ...
https://man.mtool.work/duckdb/2.0/core_extensions/spatial/gdal.html
Troubleshooting Quack 8067
DuckDB 2.0 ships a polished version of Quack (first released in DuckDB 1.5.3) with substantial performance and stability improvements. If you experience any issues with Quack, try upgrading all your DuckDB clients to the latest version of t ... g Without Attaching If you want to keep lazy resolution, use quack_query() , which runs SQL directly on the server without importing its catalog: {:.codebox-client} FROM quack_query( 'quack:localhost', 'SELECT count(*) FROM ice.demo.orders', token = 'exam ...
https://man.mtool.work/duckdb/2.0/quack/troubleshooting.html
Order Preservation 8067
For many operations, DuckDB preserves the order of rows, similarly to data frame libraries such as Pandas. Example Take the following table for example: CREATE TABLE tbl AS SELECT * FROM (VALUES (1, 'a'), (2, 'b'), (3, 'c')) t(x, y); SELECT ... ed. To change this setting, use: SET preserve_insertion_order = false; Disabling this setting can reduce memory usage when importing or exporting datasets larger than memory. See the preserve_insertion_order option in the workload tuning guide for details ...
https://man.mtool.work/duckdb/2.0/sql/dialect/order_preservation.html
PREV 1 2 3 NEXT
DuckDB 2.0 Documentation / man.mtool.work