Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DDB SQL Console Component #920

Closed
mcrascal opened this issue Jun 1, 2023 · 0 comments
Closed

DDB SQL Console Component #920

mcrascal opened this issue Jun 1, 2023 · 0 comments
Assignees

Comments

@mcrascal
Copy link
Member

mcrascal commented Jun 1, 2023

To be initially released as a component plugin, not installed in user projects by default. Smaller alternative to the new page types described in #765.

Main goal here is to bring ddb wasm out of prototypes and into production ahead of #768

<SQLConsole data={query_name} defaultQuery='select * from query_name limit 10' />

  • Implemented as a component plugin (e.g. someone could install it in their project)
  • Accepts normal query result JSON input, no parquet, no database connection impacts
  • Runs WASM DDB internally, loads the supplied data into a table
  • Defaults to select * limit 10 or similar, with option for the user supply it as a prop (e.g. defaultQuery in the above)
  • Re-execute queries on keystroke, command enter, or run query button
  • Pass results to a data table component, or a more stripped down table if data table isn't suitable
  • Loading skeleton acceptable during startup of internal ddb instance, pre-rendering as a stretch goal

For reference:

  1. https://github.com/evidence-dev/duckdb-wasm-poc/blob/master/src/routes/%2Bpage.svelte
  2. https://github.com/duckdb-wasm-examples/sveltekit-typescript
  3. https://excalidraw.com/#room=48f7c829383ba03d96cf,0htpa0HEro3nLCTtQWCh6g
@csjh csjh mentioned this issue Jun 15, 2023
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants