We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
First off, thanks for datasette. 🙏🏻
Checking Evolution's data, I've hit a snag with tables with names like [Gmail]/Inbox.
[Gmail]/Inbox
A minimal reproduction:
$ sqlite3 /tmp/slashes SQLite version 3.45.1 2024-01-30 16:01:20 Enter ".help" for usage hints. sqlite> create table "[foo]/bar" (a text); Ctrl-D $ datasette /tmp/slashes Usage: datasette serve [OPTIONS] [FILES]... Try 'datasette serve --help' for help. Error: Connection to /tmp/slashes failed check: near "/": syntax error $ datasette --version datasette, version 0.64.8
Testing further, having only [...] fails with:
[...]
$ sqlite3 /tmp/slashes SQLite version 3.45.1 2024-01-30 16:01:20 Enter ".help" for usage hints. sqlite> create table "[foo]" (a text); $ datasette /tmp/slashes Usage: datasette serve [OPTIONS] [FILES]... Try 'datasette serve --help' for help. Error: Connection to /tmp/slashes failed check: unrecognized token: "]"
In summary:
[foo]/bar
failed check: near "/": syntax error
[foo]
failed check: unrecognized token: "]"
[foo
foo]
foo/bar
sqlite3 cli itself does not have problems with any names mentioned above.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
First off, thanks for datasette. 🙏🏻
Checking Evolution's data, I've hit a snag with tables with names like
[Gmail]/Inbox
.A minimal reproduction:
Testing further, having only
[...]
fails with:In summary:
[foo]/bar
failed check: near "/": syntax error
)[foo]
failed check: unrecognized token: "]"
)[foo
foo]
failed check: unrecognized token: "]"
)foo/bar
sqlite3 cli itself does not have problems with any names mentioned above.
The text was updated successfully, but these errors were encountered: