DuckDb command not working in DataGrip but works in DuckDb CLI
Answered
If Irun this command using the DuckDB CLI it works fine:
CREATE TABLE Usage AS SELECT * FROM read_csv('Usage_2022*.txt', delim='\t',QUOTE='',HEADER=true,AUTO_DETECT=TRUE);
But when I run the same command within DataGrip query console the command fails.
Or, it runs but the parsing is not working so the header is just read in as a single VARCHAR column.
I suspect this is has to do with the tab character not being passed along to the DuckDb.
Has anyone here got any suggestions for how to fix this?
My settings are as follows
Please sign in to leave a comment.
I found out that the dialect for the driver had to be changed to SQLite. Once I did that it works fine.
Where is the data stored and for how long. when `:memory:` is used. For example:
CREATE TABLE Features ASSELECT *FROM read_json_auto('big-test.json', sample_size = -1);I may assume you're referring to the in-memory authentication to the database where you want to run the DDL statement above. It's important to note that we don't store any data and pass the commands to the database engine via the jdbc drivers. The query you're running when connected via in memory is executed without any issues (tested on DataGrip 2024.2.X ). As for the in-memory management, it's pretty much everything that applies to the vendor documentation. Please can you provide more context about your use case and the issue you're having.