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
.malloysql
I want to save the result of a Malloy view into a Postgres 13/Postgis database. As per the documentation:
>>>malloy
>>>sql
However, Malloy immediately complains about the first block opener:
mismatched input '>' expecting {<EOF>, AGGREGATE, CALCULATE, DIMENSION, GROUP_BY, JOIN_CROSS, JOIN_ONE, JOIN_MANY, MEASURE, NEST, PROJECT, QUERY, RUN, SELECT, SOURCE, VIEW, ALL, AVG, CAST, COUNT, DAY, EXCLUDE, FALSE, HOUR, IMPORT, IS, MAX, MIN, MINUTE, MONTH, NOT, NOW, NULL, PICK, QUARTER, SECOND, SOURCE_KW, SUM, TABLE, TRUE, WEEK, YEAR, HACKY_REGEX, SQ_STRING, DQ_STRING, BQ_STRING, DOC_ANNOTATION, ANNOTATION, '(', '{', '-', ';', LITERAL_TIMESTAMP, LITERAL_HOUR, LITERAL_DAY, LITERAL_QUARTER, LITERAL_MONTH, LITERAL_WEEK, LITERAL_YEAR, IDENTIFIER, NUMERIC_LITERAL, INTEGER_LITERAL, '"""'} | >>>malloy
What am I doing wrong? S.
tst.malloysql
Ubuntu 20.04
self-hosted CodeServer bare metal on Ubuntu 20.04
VS Code Extension v0.3.1714196298 (pre-release)
Postgres 13
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What happens?
I want to save the result of a Malloy view into a Postgres 13/Postgis database.
As per the documentation:
.malloysql
document>>>malloy
to define a Malloy code block>>>sql
code block.However, Malloy immediately complains about the first block opener:
What am I doing wrong?
S.
To Reproduce
tst.malloysql
document>>>malloy
OS:
Ubuntu 20.04
Malloy Client:
self-hosted CodeServer bare metal on Ubuntu 20.04
Malloy Client Version:
VS Code Extension v0.3.1714196298 (pre-release)
Database Connection:
Postgres 13
The text was updated successfully, but these errors were encountered: