Results of 1 - 2 of about 2 for gone (0.001 sec.)
- Migrating Python Code to DuckDB 2.0 11228
- This page lists what Python code written for DuckDB 1.x must change to run on DuckDB 2.0. Each item gives the 1.x form, the 2.0 form and the page that explains it. For changes outside the Python client, see Migrating to DuckDB v2.0 . Python
...execute() . 1.x: con.execute(query).fetch_arrow_table() , fetch_record_batch() , arrow() and pl() . 2.0: these methods are gone from execute() results, and to_arrow_table() and to_arrow_reader() there copy the rows and warn. Use a relation: con.sql(q...from a relation. 1.x: rel.fetchone() , rel.fetchmany(n) , rel.execute() and rel.fetch_df_chunk() . 2.0: these methods are gone, because a relation keeps no result between calls and runs its query again on every read. To keep a fetchone() or fetchman... - https://man.mtool.work/duckdb/2.0/clients/python/migration.html
- Statically Linking Extensions 7485
- This page is for client and binding authors, and for anyone who embeds libduckdb in their own application. It describes how statically linking extensions changed in DuckDB 2.0 and what builders on top of DuckDB need to do. This change is in
...r and the built-in httplib also became opt-in at link time ( duckdb#26188 ). Two aspects that earlier builds relied on are gone: The bundle-library Makefile target that merged everything into a single libduckdb_bundle.a . Extensions, httplib , and lo... - https://man.mtool.work/duckdb/2.0/dev/building/linking_extensions.html
PREV
1
NEXT
DuckDB 2.0 Documentation / man.mtool.work