This article is about the current transformation of the output parameters and how their functionality is being emulated.
Description
An output parameter is a parameter whose value is passed out of the stored procedure, back to the calling SQL block. Since the output parameters are not supported by Snowflake Scripting, a solution has been implemented in order to emulate their functionality.
Sample Source Patterns
Single OUT parameter
The most basic scenario for OUT parameters is when the procedure only has one. In this case, we simply return the OUT parameter at the end of the procedure body.
The EXEC procedure has to be translated as well, for this a CALL is created, the parameters are passed without any modifier ("OUT" is removed), and subsequently, an assignment is done so the parameter is associated with it's respective resulting value.
SQL Server
-- Procedure with output parameterCREATEPROCEDURE dbo.outmain@name VARCHAR (255) OUTPUTASSET @name ='Jane';-- Auxiliary procedure that calls the main procedureCREATEPROCEDURE dbo.outauxASDECLARE @name VARCHAR (255);EXEC dbo.outmain @name = @name OUTPUT;
Snowflake Scripting
-- Procedure with output parameterCREATE OR REPLACE PROCEDURE dbo.outmain (NAME STRING /*** MSC-WARNING - MSCEWI1083 - OUTPUT PARAMETERS ARE NOT SUPPORTED BUT FUNCTIONALITY IS BEING EMULATED ***/)
RETURNSVARCHARLANGUAGESQLEXECUTEASCALLERAS$$BEGIN --** MSC-WARNING - MSCEWI1082 - AUTO-GENERATED CODE IN ORDER TO SUPPORT OUT PARAMETERS IN SNOWFLAKE SCRIPTING **
NAME :='Jane';END;RETURNNAME;$$;-- Auxiliary procedure that calls the main procedureCREATEORREPLACEPROCEDURE dbo.outaux ()RETURNSVARCHARLANGUAGESQLEXECUTEASCALLERAS$$DECLARENAMEVARCHAR(255);BEGINCALL dbo.outmain(:NAME) /*** MSC-WARNING - MSCEWI1082 - AUTO-GENERATED CODE IN ORDER TO SUPPORT OUT PARAMETERS IN SNOWFLAKE SCRIPTING ***/
NAME := (SELECT*FROMTABLE(RESULT_SCAN(LAST_QUERY_ID())));END;$$;
Multiple OUT parameters
When more than one OUT parameters are found, the RETURNS clause of the procedure changes to VARIANT. This is to accommodate the OBJECT_CONSTRUCT that is going to be used to store the values of the OUT parameters.
On top of that, a RETURN statement is added to the end of the procedure's body. This is where the OBJECT_COSNTRUCT is created and all the OUT parameter values are stored within it. This object will then be used by the caller to assign the parameters value to the corresponding result.
CREATE OR REPLACE PROCEDURE PUBLIC.basicProc (COL1 FLOAT /*** MSC-WARNING - MSCEWI1083 - OUTPUT PARAMETERS ARE NOT SUPPORTED BUT FUNCTIONALITY IS BEING EMULATED ***/, COL2 STRING /*** MSC-WARNING - MSCEWI1083 - OUTPUT PARAMETERS ARE NOT SUPPORTED BUT FUNCTIONALITY IS BEING EMULATED ***/)
RETURNS VARIANTLANGUAGESQLEXECUTEASCALLERAS$$BEGIN COL1 :=4; COL2 :='test'; /*** MSC-WARNING - MSCEWI1082 - AUTO-GENERATED CODE IN ORDER TO SUPPORT OUT PARAMETERS IN SNOWFLAKE SCRIPTING ***/
RETURN OBJECT_CONSTRUCT('COL1', :COL1, 'COL2', :COL2);END;$$;CREATEORREPLACEPROCEDURE PUBLIC.basicProcCall ()RETURNSVARCHARLANGUAGESQLEXECUTEASCALLERAS$$DECLARE VAR1 INT :=0; VAR2 VARCHAR(10) :='EMPTY'; call_results VARIANT;BEGIN call_results := (CALL basicProc(:VAR1, :VAR2)); /*** MSC-WARNING - MSCEWI1082 - AUTO-GENERATED CODE IN ORDER TO SUPPORT OUT PARAMETERS IN SNOWFLAKE SCRIPTING ***/
VAR1 := :call_results:col1; VAR2 := :call_results:col2;INSERT INTO PUBLIC.TABLE1 (col1, col2) VALUES (:VAR1, :VAR2);END;$$;CALL basicProcCall();
OUT parameters and return values
SQL Server allows procedures to have return values. When a procedure has both a return value and OUT parameter(s), a similar approach to the Multiple OUT parameters scenario is followed. The original return value is treated as an OUT parameter would be treated, so it's stored within the OBJECT_CONSTRUCT and extracted inside the caller procedure.
SQL Server
-- Procedure with multiple output parametersCREATEPROCEDURE dbo.outmain@name VARCHAR (255) OUTPUTASSET @name ='Jane';RETURN0;-- Auxiliary procedure that calls the main procedureCREATEPROCEDURE dbo.outauxASDECLARE @name VARCHAR (255);DECLARE @returnValue INT;EXEC @returnValue = dbo.outmain @name = @name OUTPUT;
Snowflake Scripting
-- Procedure with multiple output parametersCREATE OR REPLACE PROCEDURE dbo.outmain (NAME STRING /*** MSC-WARNING - MSCEWI1083 - OUTPUT PARAMETERS ARE NOT SUPPORTED BUT FUNCTIONALITY IS BEING EMULATED ***/)
RETURNS VARIANTLANGUAGESQLEXECUTEASCALLERAS$$BEGINNAME :='Jane'; /*** MSC-WARNING - MSCEWI1082 - AUTO-GENERATED CODE IN ORDER TO SUPPORT OUT PARAMETERS IN SNOWFLAKE SCRIPTING ***/
RETURN OBJECT_CONSTRUCT('SC_RET_VALUE', 0, 'NAME', :NAME);END;$$;-- Auxiliary procedure that calls the main procedureCREATEORREPLACEPROCEDURE dbo.outaux ()RETURNSVARCHARLANGUAGESQLEXECUTEASCALLERAS$$DECLARENAMEVARCHAR(255); RETURNVALUE INT;BEGINCALL dbo.outmain(:NAME) /*** MSC-WARNING - MSCEWI1082 - AUTO-GENERATED CODE IN ORDER TO SUPPORT OUT PARAMETERS IN SNOWFLAKE SCRIPTING ***/
LET call_results VARIANT := (SELECT*FROMTABLE(RESULT_SCAN(LAST_QUERY_ID()))); RETURNVALUE :=GET(:call_results, 'SC_RET_VALUE');NAME :=GET(:call_results, 'NAME');END;$$;
Customer data type OUT parameters
when the output parameter is a customer type, the process is similar to a regular data type.
CREATE OR REPLACE PROCEDURE procedure_udtype_out_params (P_EMPLOYEE_ID INT, P_PHONE dbo.PhoneNumber /*** MSC-ERROR - MSCEWI4059 - DATA TYPE DBO.PHONENUMBER IS NOT SUPPORTED IN SNOWFLAKE ***/ /*** MSC-WARNING - MSCEWI1083 - OUTPUT PARAMETERS ARE NOT SUPPORTED BUT FUNCTIONALITY IS BEING EMULATED ***/)
RETURNSTABLE()LANGUAGESQLEXECUTEASCALLERAS$$DECLARE ProcedureResultset RESULTSET;BEGIN ProcedureResultset := (SELECT phoneINTO :P_PHONEFROM employeesWHERE employee_id = :P_EMPLOYEE_ID);RETURNTABLE(ProcedureResultset);--** MSC-WARNING - MSCEWI1082 - AUTO-GENERATED CODE IN ORDER TO SUPPORT OUT PARAMETERS IN SNOWFLAKE SCRIPTING **--** MSC-WARNING - MSCEWI4072 - RETURN statement will be ignored due to previous RETURN statement **RETURN P_PHONE;END;$$;