Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Major |
| Complexity | Unknown |
| Component | Editor - Debugger for Sybase |
| Version | 17.0 |
Product: Aqua Data Studio
Version: 17.0.0-ga-34
CREATE TABLE "dbo"."Employee" ( "emp_id" bigint NULL,"name" varchar(25) NULL,"salary" bigint NULL )LOCK ALLPAGESGOINSERT INTO "dbo"."Employee"("emp_id","name","salary") VALUES(1,'Nilesh',5000)GOINSERT INTO "dbo"."Employee"("emp_id", "name", "salary") VALUES(2, 'kirti', 7000)GOINSERT INTO "dbo"."Employee"("emp_id", "name", "salary") VALUES(2, 'Tariq', 7000)GOCREATE PROCEDURE "dbo"."SP_employee"( @id bigint, @f_name varchar(25), @salary int OUTPUT ) ASBEGIN SELECT "emp_id", "name", "salary" FROM "dbo"."Employee"ENDGOsp_procxmode '"dbo"."SP_employee"', 'Unchained'GOdeclare @RETURN_VALUE int declare @id bigint declare @f_name varchar(25) declare @salary int EXECUTE @RETURN_VALUE = dbo.SP_employee @id = 1,@f_name = 'Nilesh',@salary = 5000 output|
|
449 KB
@ivan: could be due to your changes in svn#46915
snv#46915 fixed an extraction issue. Status2 bit column was not correctly extracted and used to determine if the procedure had an output parameter. Unfortunately we have multiple areas that script the procedure in slightly different ways. the script debugger script is using a format where the execute command is using syntax [@variable = <value>, ...] and after the check in the output parameter is then assigned if it was created with it. Documentation states that if the output parameter is used we will have to use the
Declare @variable
SELECT @variable = <value>
execute using syntax [@variable, ....] without passing a constant. I will need to make changes to use this syntax method now that we are correctly extracting the output parameter value. Studying to see what code changes need to occur and impact for testing.
snv#46915 fixed an extraction issue. Status2 bit column was not correctly extracted and used to determine if the procedure had an output parameter. Unfortunately we have multiple areas that script the procedure in slightly different ways. the script debugger script is using a format where the execute command is using syntax [@variable = <value>, ...] and after the check in the output parameter is then assigned if it was created with it. Documentation states that if the output parameter is used we will have to use the
Declare @variable
SELECT @variable = <value>
execute using syntax [@variable, ....] without passing a constant. I will need to make changes to use this syntax method now that we are correctly extracting the output parameter value. Studying to see what code changes need to occur and impact for testing.
Script debugger create has been modified so that if there is an output parameter, the variables will be set before sent in the execute statement and not set inside the execute statement.
What this means is in the example above the script will look like this:
Script debugger create has been modified so that if there is an output parameter, the variables will be set before sent in the execute statement and not set inside the execute statement.
What this means is in the example above the script will look like this:
Issue #14231 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build v16.0.14, v17.0.0-ga-36, v18.0.0-dev-36 |
| No time estimate |
1 issue link |
is broken by #13839
Issue #13839Sybase ASE -> Stored procedures paramaters [in/out] settings not extracted |
@ivan: could be due to your changes in svn#46915