There are two possible solutions:
set @z
to null in the very beginning of your loop (prior to SET @sql_text2 = concat('
....)
or instead of
SELECT id INTO @z FROM table_name WHERE id >= 7000 ORDER BY id LIMIT 1000,1;
use this:
SET @z = (SELECT id FROM table_name WHERE id >= 7000 ORDER BY id LIMIT 1000,1);
Explanation:
When no row is found, the variable is unchanged from its previous value... so it's not that you have to "set it to null before you use it," it's that you have to reset it to null before you use it again, if you are doing something like SELECT ... INTO
that won't reset the value if nothing is found.
see: https://dba.stackexchange.com/a/35207/12923
I think these answers are all getting a) way too complicated, and b) off-track relative to what user2023861 wants to accomplish:
"I am trying to declare a variable, then select that variable." means two different things in either PL/SQL or in SQLplus, and perhaps two more things in DBArtisan. To accomplish the objective in SQLplus, use "Substitution variables"...excellent background is found here.
My example, doesn't precisely follow your SQL Server T-SQL example, but it's close and is NOT procedural (read: no anonymous PL/SQL block.)
PL/SQL with Substitution variables:
DEFINE min_salary = 1000
DEFINE mgrID = 7
select *
from employees
where
salary > &min_salary
and mgrID = &mgrID
;
All at the SQL-Plus prompt....from my fictional employees table, I got this result:
SALARY MGRID
---------- ----------
2000 7
1001 7
2 row selected.
If you want to make this semi-procedural, then you use BIND Variables and the declarative syntax of PL/SQL similar to T-SQL. (In my opinion this is a HUGE waste of effort, but is included to help clarify variable types.)
SQLPlus using PL/SQL Bind variables:
VARIABLE v_in_min_salary number;
VARIABLE v_mgrID number; /* vars are defined within SQL+ */
VARIABLE v_out_salary number;
VARIABLE v_out_mgrID number;
BEGIN
:v_in_min_salary := 1000; /* vars are assigned values in PL/SQL */
:v_mgrID := 7;
select salary, mgrID
into :v_out_salary, :v_out_mgrID
from employees
where salary > :v_in_min_salary and mgrID = :v_mgrID
;
end;
/
PRINT :v_in_min_salary /* here the in and out vars are displayed */
PRINT :v_mgrID
PRINT :v_out_salary
PRINT :v_out_mgrID
Fully-procedural approach using PL/SQL:
set serveroutput on; /* environment setting within SQLplus to see output */
DECLARE
v_in_min_salary number := 1000;
v_mgrID number :=7;
v_out_salary number;
v_out_mgrID number;
BEGIN
SELECT salary, mgrID
into :v_out_salary, :v_out_mgrID
from employees
where salary > :v_in_min_salary and mgrID = :v_mgrID
;
DBMS_OUTPUT.PUT_LINE('Salary Output is= '||:v_out_salary);
DBMS_OUTPUT.PUT_LINE('Manager ID = '||:v_out_mgrID);
END;
/
So, when do I use each case? I use SQLplus Substitution variables 75% of the time when I write SQL scripts that I want to parameterize the input for. Executing a script at the SQLplus prompt allows passing inbound arguments, so my favorite Substitution variables are &1 and &2 as in the following example:
@get_table_size.sql <schema> <table_name>
which in practice becomes
@get_table_size jason employees
and executes SQL code similar to
SELECT extents
FROM all_tables
WHERE UPPER(table_owner) = upper('&1') /* inbound first argument */
and UPPER(table_name) = upper('&2') /* inbound 2nd argument */
;
Notice how the inbound arguments are assigned into substitution variables, then used in the SQL statement. I never use the middle example, and I always use the 3rd examples (procedural PL/SQL) when writing functions, procs, and packages.
Best Answer
Yes, 'W' will do that -- replace the file. Use 'A' to append. I don't think you can "modify in place"; you might have to copy the file to a new one making the changes you desire, delete the original and then rename the copy.
All of this begs the question why you're trying to do all of this in PL/SQL. It might be better -- certainly easier -- to do it in an external program written in eg Python and invoke that.