Can't execute current statement when certain statement precedes it

Discussion of open issues, suggestions and bugs regarding database management and development tools for SQL Server
Post Reply
Thenrich
Posts: 109
Joined: Sun 21 Dec 2014 19:47

Can't execute current statement when certain statement precedes it

Post by Thenrich » Fri 08 Nov 2019 00:48

I have code like this:

alter procedure x
as
begin
...
end

; select * from table;

When the cursor is inside the select statement and I execute current statement it doesn't get executed. When I remove the alter statement, it gets executed. My understanding is that when I have a semi column before my statement, it isolates my statement from prior statements. It works if the alter is another select for example.

Why doesn't it work with certain previous statements like an alter procedure?

Using SQL Complete 6.2.37.

alexa
Devart Team
Posts: 2858
Joined: Fri 24 Jun 2011 14:17

Re: Can't execute current statement when certain statement precedes it

Post by alexa » Mon 11 Nov 2019 10:39

We were able to reproduce this issue and will fix it in one of the next product builds.

We will notify you once it's available for downloading.

Thenrich
Posts: 109
Joined: Sun 21 Dec 2014 19:47

Re: Can't execute current statement when certain statement precedes it

Post by Thenrich » Mon 11 Nov 2019 17:57

I would like to add also that if my statement is enclosed between two semicolons, it should be isolated and I should be able to execute it regardless if the SQL that comes before or after it has syntax errors. It should not care.

Thenrich
Posts: 109
Joined: Sun 21 Dec 2014 19:47

Re: Can't execute current statement when certain statement precedes it

Post by Thenrich » Fri 27 Dec 2019 19:05

This issue has not been resolved in the latest release 6.3.16.

alexa
Devart Team
Posts: 2858
Joined: Fri 24 Jun 2011 14:17

Re: Can't execute current statement when certain statement precedes it

Post by alexa » Mon 30 Dec 2019 10:48

We do apologize for the delay on this.

Our developers team has reviewed this issue and decided to move the fix forward to one of the next product versions since it requires significant changes in the program code.

Post Reply