Giters
tursodatabase
/
libsql-shell-go
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
7
Watchers:
2
Issues:
82
Forks:
7
tursodatabase/libsql-shell-go Issues
.dump causes an error
Updated
5 months ago
Comments count
2
.schema may print uglified version of table
Updated
5 months ago
Support for executing files
Updated
6 months ago
Comments count
1
Support multi-statement, multi-line transactions
Updated
7 months ago
Comments count
1
Autocomplete on empty input panics
Updated
9 months ago
Use /dump endpoint instead of custom implementation for .dump
Updated
a year ago
SQL runtime errors are missing a proper error message
Updated
a year ago
Comments count
5
Add a way to import CSV data into a table
Updated
a year ago
.dump generates invalid NULL in output for tables that have a UNIQUE constraint
Updated
a year ago
.dump doesn't use a transaction (sqlite3 does)
Updated
a year ago
Errors with input from multiple statements coming from stdin, .read, or CLI arg are unhelpful
Updated
a year ago
Don't pass the auth token in the database URL query string
Closed
a year ago
Comments count
1
All lines of `.schema` output have the same length (trailing space padding on every line)
Updated
a year ago
Creating triggers is not possible because a semicolon in SQL block terminates the entire command
Closed
a year ago
Comments count
1
Block comments with semicolon + NL don't work when pasted into interactive shell
Closed
a year ago
Line comments are not fully ignored, causes errors (incompatible with sqlite3)
Closed
a year ago
Improve the output of EXPLAIN QUERY PLAN
Updated
a year ago
Messy history with multi-line commands
Updated
a year ago
Comments count
1
`.schema` command should show SQL with terminating semicolons
Closed
a year ago
`.schema` should show views
Closed
a year ago
`.schema` output should show triggers
Closed
a year ago
Comments count
1
Internal commands should use statements with parameters, or correctly escape values
Closed
a year ago
Missing auth token in URL against a Turso db yields confusing error "failed to execute SQL: SELECT 1; invalid character 'T' looking for beginning of value"
Updated
a year ago
`.dump` doesn't properly escape strings with single quotes
Closed
a year ago
Comments count
1
Parse semicolons correctly when creating triggers
Closed
a year ago
Comments count
1
Copying text on shell should not include shell prompt
Updated
a year ago
`.dump` outputs invalid `NULL;` on table with UNIQUE column
Closed
a year ago
Comments count
1
Change `DbPath` configuration name
Closed
a year ago
Fix: TestRootCommandShellSuite_WhenDbIsSqld fails when running against either local or remote sqld database
Closed
a year ago
Comments count
1
Should shell `.dump` use a transaction?
Closed
a year ago
Comments count
2
Add transactions to .dump command
Updated
a year ago
Comments count
2
`.dump` produces broken `NULL;` statement when `UNIQUE` constraint is present
Closed
a year ago
Add `--auth` flag
Closed
a year ago
Fix suggestion: insert i
Updated
a year ago
Comments count
1
`.mode` command has insuffient help
Closed
a year ago
Configure CI to run tests on a sqld server
Closed
a year ago
`--help` flag is not properly disabled
Updated
a year ago
No way to cancel a shell.RunShellLine call
Closed
a year ago
Change Turso tests to sqld tests
Closed
a year ago
Development on the shell should not require Turso and should minimize dependence on it
Closed
a year ago
Comments count
1
Explicit say on README that Git hooks are optional
Updated
a year ago
Add option to pass Bearer token as ShellConfig
Closed
a year ago
Comments count
1
shell.RunShellLine should not testConnection
Closed
a year ago
Add number of rows changed to shell results
Updated
a year ago
Fix suggestion: select 1 from table3; select 1 f
Updated
a year ago
Autocomplete SQL keywords
Closed
a year ago
Implement .dump filter by objects
Updated
a year ago
Missing instructions on running project inside README.md
Updated
a year ago
Have a bootstrap shell script
Updated
a year ago
New command: .dump
Closed
a year ago
Previous
Next