Stored procedure changes reverted on error in v4
Posted: Thu 04 Dec 2014 16:39
I've tried to submit this to support including my software settings as an attachement but I have not received a confirmation that it has been received.
I have experienced a serious issue since the update to v4. It seems that when I edit an existing stored procedure and there is an error in my changes, dbForge will revert the stored procedure to the most recent saved version. This does not happen in every case. It seems to happen in procedures with more than 1 select statement. For example, create the following procedure. Then open it to edit from the database view. Uncomment the declare statement to include a syntax error and click "Update Database" to save the change. For me, there is no error displayed and the declare statement will revert to the commented state.
I have experienced a serious issue since the update to v4. It seems that when I edit an existing stored procedure and there is an error in my changes, dbForge will revert the stored procedure to the most recent saved version. This does not happen in every case. It seems to happen in procedures with more than 1 select statement. For example, create the following procedure. Then open it to edit from the database view. Uncomment the declare statement to include a syntax error and click "Update Database" to save the change. For me, there is no error displayed and the declare statement will revert to the commented state.
Code: Select all
CREATE PROCEDURE dbo.spLookupSiteId
@site_id int output
AS
begin
set nocount on
--DECLARE @foo INTX
select @site_id = 2
select @site_id = 1
return 0
end
GO