You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm building a system to enable querying data stored in mysql from duckdb-wasm, idea is to reduce cpu load on the mysql server by offloading querying logic to the client side.
For this to work i have to expose data (table's/views) from mysql to duckdb, currently i'm using sending csv files for each table/view manually but now i want to explore something faster.
Should i look at duckdb mysql extension?, send parquet files or even duckdb db for each table/view?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm building a system to enable querying data stored in mysql from duckdb-wasm, idea is to reduce cpu load on the mysql server by offloading querying logic to the client side.
For this to work i have to expose data (table's/views) from mysql to duckdb, currently i'm using sending csv files for each table/view manually but now i want to explore something faster.
Should i look at duckdb mysql extension?, send parquet files or even duckdb db for each table/view?
Beta Was this translation helpful? Give feedback.
All reactions