[Feat]: Cross Connection Notebook
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 46/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- sql, typescript
Research direction
Start by reading the notebook flow for selecting a connection and executing a query, then trace how a result variable such as {{cell3}} is passed into another query. The issue does not name files or tests, so locate those entry points in the project first. Done means a notebook can use different connections and pass one cell's result as input to a query on another connection.
Written by the indexing model from the issue text.
Description
Prerequisites
- I have written a descriptive issue title
- I have searched existing issues to ensure the feature has not already been requested
🚀 Feature Proposal
Right now notebook can connect to multiple schemas/dbs of the same connection.
Request it to support a global notebook which can connect to any connection.
Motivation
We cannot do cross connection joins.
But if notebooks works across connections, then I can use result variable like {{cell3}} from one connection and pass that as input to another query in different connection.
Example
No response
- Dominant language
- TypeScript
- Stars
- 5.1k
- Forks
- 335
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 62
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TabularisDB/tabularis
-
feature request good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
TabularisDB/tabularis#853 ·
Maintainers usually reply within 1 day
-
Update the logo across the app: icons, dock, installers and in-app brandingPossibly taken @wajrock claimed this today. Openenhancement
TabularisDB/tabularis#873 · 1 assignee ·
Maintainers usually reply within 1 day
-
feature request help wanted
Difficulty 4/5 3-5 days Newbie friendliness 68/100
TabularisDB/tabularis#871 ·
Maintainers usually reply within 1 day
-
feature request good first issue
Difficulty 3/5 1-2 days Newbie friendliness 74/100
TabularisDB/tabularis#870 ·
Maintainers usually reply within 1 day
-
feature request help wanted
Difficulty 4/5 3-5 days Newbie friendliness 58/100
TabularisDB/tabularis#869 ·
Maintainers usually reply within 1 day
All issues in TabularisDB/tabularis
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
wardian-app/Wardian#1603 ·
Maintainers usually reply within 1 day
-
Sign the pledgeOpen
Difficulty 1/5 Under an hour Newbie friendliness 85/100
input-output-hk/devx-updates#168 ·
Maintainers usually reply within 1 day
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
github/docs#46222 · 1 comment ·
Maintainers usually reply within 1 day
-
agent-ready area: config area: skills type: chore upstream: brain-kit
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
dev experience frontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cuttle-cards/cuttle#1403 ·
Maintainers usually reply within 1 day