Results of 1 - 3 of about 3 for asset (0.001 sec.)
- ODBC API on Windows 11924
- Setup Using the DuckDB ODBC API on Windows requires the following steps: Microsoft Windows requires an ODBC Driver Manager to manage communication between applications and the ODBC drivers. The Driver Manager on Windows is provided in a DLL
...iles and tools. For detailed information check out the Common ODBC Component Files . DuckDB releases the ODBC driver as an asset. For Windows, download it from the Windows ODBC asset (x86_64/AMD64) . The archive contains the following artifacts: duckd... - https://man.mtool.work/duckdb/2.0/clients/odbc/windows.html
- ODBC API on Linux 7980
- Driver Manager A driver manager is required to manage communication between applications and the ODBC driver. We tested and support unixODBC that is a complete ODBC driver manager for Linux. Users can install it from the command line: On De
...ributions (Amazon Linux, RHEL, CentOS, etc.), run: sudo yum install unixODBC Setting Up the Driver Download the ODBC Linux Asset corresponding to your architecture: x86_64 (AMD64) arm64 (AArch64) The package contains the following files: libduckdb_odb... - https://man.mtool.work/duckdb/2.0/clients/odbc/linux.html
- Instantiate 7980
- Overview DuckDB-Wasm can be instantiated in several ways, depending on how your application bundles and serves its assets. Each approach resolves the mainModule (the WebAssembly file) and the mainWorker (the worker script) for the browser's
...bjectURL(worker_url); webpack When your application is built with webpack , let the bundler resolve and emit DuckDB-Wasm's assets instead of fetching them from a CDN. Import each .wasm module directly, and reference the worker scripts with new URL(......new duckdb.AsyncDuckDB(logger, worker); await db.instantiate(bundle.mainModule, bundle.pthreadWorker); vite Vite resolves assets a little differently: appending the ?url suffix to an import tells Vite to return the asset's final URL rather than its c...uckdb/duckdb-wasm/dist/ , serve them from your own origin, and point the bundle paths at those locations. This keeps every asset on your own server, which suits offline, air-gapped, or strict content-security-policy deployments. Update the placeholder... - https://man.mtool.work/duckdb/2.0/clients/wasm/instantiation.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work