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
Hi there 👋,
I’m building a simple, fully serverless web app that runs duckdb-wasm entirely in the browser, and I’d love to leverage DuckLake for durable storage (persisting the database to S3/GCS). This would let me keep all my logic in the frontend and offload persistence to object storage, without needing a separate back end.
However, I haven’t found any examples or documentation showing how to hook DuckLake up to a browser environment. I suspect that it’s only supported on the non-WASM clients at the moment.
Is client-side usage of DuckLake with duckdb-wasm supported (or planned)?
I’d really appreciate any pointers, examples, or links to ongoing discussions. Thanks in advance for your help!
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
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there 👋,
I’m building a simple, fully serverless web app that runs duckdb-wasm entirely in the browser, and I’d love to leverage DuckLake for durable storage (persisting the database to S3/GCS). This would let me keep all my logic in the frontend and offload persistence to object storage, without needing a separate back end.
However, I haven’t found any examples or documentation showing how to hook DuckLake up to a browser environment. I suspect that it’s only supported on the non-WASM clients at the moment.
Is client-side usage of DuckLake with duckdb-wasm supported (or planned)?
I’d really appreciate any pointers, examples, or links to ongoing discussions. Thanks in advance for your help!
Beta Was this translation helpful? Give feedback.
All reactions