Docs: CREATE GRAPH page says `USE my_graph`, but the working statement is `USE GRAPH my_graph`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
Open the CREATE GRAPH documentation page linked in the issue and find the two examples that use USE my_graph;. Change them to USE GRAPH my_graph; and explain that USE GRAPH main returns to the default graph. Also document that the current graph is shared across connections on a Database; consider the repository test test/test_files/graph/typed_subgraph.test as a reference. Done when the examples and sharing behavior are accurate.
Written by the indexing model from the issue text.
Description
Description
The CREATE GRAPH page gives USE my_graph; both for switching into a new subgraph and in its "Switch between subgraphs" section. On @ladybugdb/core 0.22.3 and 0.23.0-dev.20261105 (Node binding run under Bun 1.4.4, macOS arm64 and Linux arm64), that statement fails:
CREATE GRAPH my_graph -> Created graph successfully.
USE my_graph -> Runtime exception: No database named my_graph.
USE GRAPH my_graph -> Used graph successfully.
USE name resolves an attached database (DatabaseManager::setDefaultDatabase), not a subgraph. The repository's own test, test/test_files/graph/typed_subgraph.test, uses USE GRAPH typed_ka and returns with USE GRAPH main.
Suggested change: use USE GRAPH my_graph; in both places, and document USE GRAPH main as the way back to the default graph. It would also help to say that the current graph is shared by every connection on a Database (see the related bug report), since a reader of this page would likely assume it is per connection.
Link
https://docs.ladybugdb.com/cypher/data-definition/create-graph/
- Dominant language
- C++
- Stars
- 1.8k
- Forks
- 148
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 176
Getting set up
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 LadybugDB/ladybug
-
Bug: `USE GRAPH` on one connection changes the current graph for every connection on the DatabaseOpen
Difficulty 4/5 3-5 days Newbie friendliness 54/100
Maintainers usually reply within 1 day
-
Bug: a filtered scan reads ALP-compressed DOUBLE exceptions as 0.0 when a batch straddles a segment boundaryPossibly taken @jfrench9 claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Process aborts on a null ValueVector dereference during a relink rollback test (0.20.4, GCC 15)Possibly taken @adsharma claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 20/100
LadybugDB/ladybug#1536 · 8 comments ·
Maintainers usually reply within 1 day
-
Bug: primary-key match over an Arrow rel table also returns the first node's relsPossibly taken @zahariash claimed this 1 day ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 1-2 days Newbie friendliness 54/100
Maintainers usually reply within 1 day
All issues in LadybugDB/ladybug
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
godotengine/godot#125272 ·
Maintainers usually reply within 1 day
-
bug impact: performance priority: med review: 2026-11 severity: med
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mgradwohl/ModernLife#67 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
games-on-whales/wolf#569 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cloudflare/workerd#8290 ·
Maintainers usually reply within 1 day
-
arch-based bug mango
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
noctalia-dev/noctalia#5293 ·
Maintainers usually reply within 1 day