[Bug]: Adding whitespace to query triggers error

[doctomlug]

[Bug]: Adding whitespace to query triggers error

[doctomlug]

This is the "test case" and it works as expected with or without new-line after the SET

CREATE table IF NOT EXISTS test (a,b,c);

INSERT INTO test (a,b,c) VALUES
  ('1a','2b','3c'),
  ('4a','5b','6x');

UPDATE test SET 
a = b WHERE c = '6x';

SELECT * FROM test;

[chrisjlocke]

Can you reproduce it all the time in the same database?

I've created a minimal schema based on your query which runs without problems, albeit Win 10 rather then Win 11, but I can't see that being an issue.

[chrisjlocke]

For the avoidance of doubt (as I do get the error if the last line is highlighted) nothing is highlighted, and you're pressing the [>] button (or pressing [F5])?

If you highlight the last line and press [>] then you get the error you mentioned.

This is as expected, as pressing the [>] button runs the highlighted SQL, which in the case of highlighting just the second line, is incorrect SQL.

[doctomlug]

Thanks for the quick reaction.

The simple test I performed (see above) worked with the "test" table created in the same database file. During development I had to reconnect the DB often and reconnected to a freshly generated one (by batch process). I do not believe the database is the problem.

I am pretty sure, nothing was highlighted and I started the querry by clicking on the "execute line" toolbar or Shif-F5. Both cases had the same issue. I copied the querry from an external text edito into a fresh SQL tab to ensure no strange hidden chars are around. Same effect.

But I will check again as soon as I have access to my work computer after the weekend

(And yes, I am sure too that this is not a real bug but some other stupid issue)

[doctomlug]

• Reopen database on different PC (Win 10)
• Copied query from this forum
• Result with cursor at beginning of second line + click on "execute line"

• Result with same cursor position but click on "execute SQL" (no other query than the visible one)

In both cases nothing highlighted. I expected "execute line" to run the entire query up to the next semicolon (like it is done in Beaver). I am not sure if "line" is meant to be just this line of text or this query.

Tested a select query

Click on "execute line" ran the complete query although the cursor is in the second line

Splitting it even further, cursor in line 6, makes no difference (as expected whitespace is ignored, query is expanded "backwards" to its start)

The behavior of the two cases is clearly different and is not as expected in the case at the top.
The parsing appears to be different.

What is intended by design?