Running query in a block without highlighting no longer works

[clemlaugit]

Description

previous behaviour: if your cursor was within a block of sql, it would run all the sql that was together (i.e. no gaps between the code lines)

current behaviour: if you have some code and then a gap and more code and try to run the code block without highlighting it errors now.

see screenshot below

i added "qqqq" to the code but have a line separating the code block. I tried to execute the code without highlighting and now it errors out.

version

DBeaver Version

24.0.4.202405051837

Operating System

Mac Sonoma 14.3

Database and driver

snowflake

Steps to reproduce

write a sql statement

add a carriage return
type anything

go to your sql statement and execute without highlighting

Additional context

write a sql statement

add a carriage return
type anything

go to your sql statement and execute without highlighting

[E1izabeth]

DBeaver provided a new mode of statements execution. You can find it in preferences Editors->SQL Editor->SQL Processing->Blank line is statement delimiter. With this mode DBeaver takes everything between the statement start and the query delimiter or a new statement start. If such behavior doesn't fir your use cases, you can turn it off by switching this setting to Always.

[c-o-m-m-a-n-d-e-r-d-a-t-a]

Only chipping in as this was the latest issue on Git, and I saw it as well, but for me it was that this setting was set to 'smart' (by default?), and this rarely seemed to detect blank lines correctly. Setting to 'Always' fixed it, as per E1izabeth's note above.

[E1izabeth]

@c-o-m-m-a-n-d-e-r-d-a-t-a we had a bug in 24.0.3 version. It's fixed now.

[c-o-m-m-a-n-d-e-r-d-a-t-a]

Ok :) Although I will say that leaving the setting on 'Smart', which I don't remember doing manually, causes the blocks not to execute individually most times. Just saying :) PS this is on v 24.0.4

[E1izabeth]

We can't reproduce it. Please provide a footage of the issue.

[c-o-m-m-a-n-d-e-r-d-a-t-a]

[E1izabeth]

Thank you for providing an example. I still can't reproduce it, but hope we will figure out, what';s wrong eventually.

java_eTlP1Rz2wP.mp4

[E1izabeth]

@c-o-m-m-a-n-d-e-r-d-a-t-a I suppose your case is more about this issue #29942

[c-o-m-m-a-n-d-e-r-d-a-t-a]

I don't think so - they had set the dropdown to 'never' hadn't they? I think my issue is that 'smart' is the default (or became it silently?) and that it doesn't always work (for me, at any rate). Sometimes it does, sometimes it doesn't. Basically a more complex query will cause 'smart' to fail.

[E1izabeth]

We're going to set it back to Always by default in the next version.

[c-o-m-m-a-n-d-e-r-d-a-t-a]

Probably safest, thanks. I suppose we users don't know the exact logic of 'smart' so it doesn't always do what we expect.

Thanks again :)

[clemlaugit]

Thanks Elizabeth. Yes it was set to smart which doesn't really work.

…

On Thu, May 9, 2024 at 11:49 PM Elizabeth ***@***.***> wrote: DBeaver provided a new mode of statements execution. You can find it in preferences Editors->SQL Editor->SQL Processing->Blank line is statement delimiter. With this mode DBeaver takes everything between the statement start and the query delimiter or a new statement start. If such behavior doesn't fir your use cases, you can turn it off by switching this setting to Always. — Reply to this email directly, view it on GitHub <#30136 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AV2DKCMQ5CZR7P5DC6G7BW3ZBRUV3AVCNFSM6AAAAABHPKE2YKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBTHE3TQMZYGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Clem Lau Senior Data Engineer Learn more about DoorDash Engineering here <https://doordash.engineering/>