Closed richb-hanover closed 1 month ago
When you comment, then uncomment it leaves an area of text highlighted. So when you press control+E it is then running an empty or bad query. I think that's what's happening here.
I can recreate the error when I query an empty string.
Good sleuthing!
I'm glad I mentioned the bit about using Cmd-/. I was only doing this to ensure that I was using 3.10. But of course, I now see that qStudio only sends the single commented-out line.
I am now groping for a solution - I don't think this is anything qStudio could (reasonably) address, so I will submit a request over at PRQL.
PS @ryanhamilton Could I ask a favor? You posted two issues on PRQL, both of which have been addressed. Would you close them? Many thanks. https://github.com/PRQL/prql/issues/4540 and https://github.com/PRQL/prql/issues/4502
I changed my mind. I made a proposal at #90 that qStudio could implement. Thanks
Using qStudio 3.10 on macOS 12.7.5. I get this error when I first launch qStudio. I have a PRQL query (below) that auto-opens in the top pane. The Console also auto-opens.
To demonstrate the problem, click in the PRQL query, hit Cmd-/ to comment a line, and then again to uncomment, then hit Cmd-E to run the query. This gives the error message above. This is repeatable as many times as I like.
I can get rid of the error message by:
Then Cmd-E compiles the PRQL query and runs the SQL. If you want to test against the database, use Property_In_Lyme.sqlite
PRQL Query
Log file - the interesting exception is BEFORE the SQL code