Bind variables + SQL Developer

Hi,
I have a couple of very simple pl/sql scripts with bind variables (there are no cursors in the scripts) - when I execute these scripts in SQL Developer, it doesn't work as it should.
It seems as if SQL developer doesn't register the bind variables - in one script, the first execution worked ok, but after that I need to comment the bind variable declarations, otherwise it does not work. In the other script, NULL value is assigned to the variable eventhough a number literal was assigned to the variable.
When I execute the scripts in SQL*PLUS, they work just fine!
Why is this? Is there something I need to know inorder to use bind variables in SQL Developer?
Thanks!

Once you use '&&', the only way to 'reset' the variables is by using UNDEFINE (just like SQL*Plus).
...Unless you run a second script from a second Tab within SQLDeveloper and the second script references the '&&' variables from the first. Then, you get prompted again. In this case, it doesn't seem to see the same '&&' variables that are set in the first script. The second tab seems to have it's own "state" -- something that doesn't happen in SQL*Plus because.......well, it doesn't have tabs.
--s

Similar Messages

Schema Binding with VSS in SQL Developer

Hi guys is it possible to bind a Sql Developer or TOAD with Visual Source Safe or i can change database object in toad or sql developer and check in into VSS?
Thanks
Purvik

TOAD can do version control with any software that uses Microsoft's Source Code Control (SCC) API, which includes VSS. Look at the help pages for more info.
While SQL Developer only supports Subversion and CVS directly, I've used its External Tools capability to add ClearCase check out, check in, undo check out, and add capabilities. If you can do basic version control operations from the command line with Visual SourceSafe, you ought to be able to do the same thing. Just look up the syntax for the command line tools, and build your commands by selecting the Tools menu, select External Tools, and add a new tool. This is very much like creating a new desktop shortcut in Windows.

How to pass a list as bind variable?

How can I pass a list as bind variable in Oracle?
The following query work well in SQL Developer if I set ":prmRegionID=2".
SELECT COUNTRY_ID,
COUNTRY_NAME
FROM HR.COUNTRIES
WHERE REGION_ID IN (:prmRegionID);
The problem is that I can't find how to set ":prmRegionID=2,3".
I know that I can replace ":prmRegionID" by a substitution variable "&prmRegionID". The above query work well with"&prmRegionID=2" and with "&prmRegionID=2,3".
But with this solution, I lost all advantage of using binds variables (hard parse vs soft parse, SQL injection possibility, etc.).
Can some one tell me what is the approach suggest by Oracle on that subject? My developer have work a long time too find how but didn't found any answer yet.
Thank you in advance,
MB

Blais wrote:
The problem is that I can't find how to set ":prmRegionID=2,3".Wrong problem. Setting the string bind variable to that means creating a single string that contains the text "+2,3+". THE STRING DOES NOT CONTAIN TWO VALUES.
So the actual problem is that you are using the WRONG data type - you want a data type that can have more than a single string (or numeric) value. Which means that using the string (varchar2) data type is the wrong type - as this only contains a single value.
You need to understand the problem first. If you do not understand the problem, you will not realise or understand the solution too.
What do you want to compare? What does the IN clause do? It deals with, and compares with, a set of values. So it needs a set data type for the bind variable. A set data type enables you to assign multiple values to the bind variable. And use this bind variable for set operations and comparisons in SQL.
Simple example:
SQL> --// create a set data type
SQL> create or replace type TStringSet is table of varchar2(4000);
2 /
Type created.
SQL>
SQL>
SQL> var c refcursor
SQL>
SQL> --// use set as bind variable
SQL> declare
2          names   TStringSet;
3 begin
4          --// assign values to set
5          names := new TStringSet('BLAKE','SCOTT','SMITH','KING');
6
7          --// use set as a bind variable for creating ref cursor
8          open :c for
9                  'select * from emp where ename in (select column_value from TABLE(:bindvar))'
10          using names;
11 end;
12 /
PL/SQL procedure successfully completed.
SQL> print c
     EMPNO ENAME      JOB              MGR HIREDATE                   SAL       COMM     DEPTNO
      7698 BLAKE      MANAGER         7839 1981/05/01 00:00:00       2850                    30
      7788 SCOTT      ANALYST         7566 1987/04/19 00:00:00       3000                    20
      7369 SMITH      CLERK           7902 1980/12/17 00:00:00        800                    20
      7839 KING       PRESIDENT            1981/11/17 00:00:00       5000                    10
SQL>
SQL> --// alternative set comparison
SQL> declare
2          names   TStringSet;
3 begin
4          --// assign values to set
5          names := new TStringSet('BLAKE','SCOTT','SMITH','KING');
6
7          --// use set as a bind variable for creating ref cursor
8          open :c for
9                  'select * from emp where TStringSet(ename) submultiset of (:bindvar)'
10          using names;
11 end;
12 /
PL/SQL procedure successfully completed.
SQL> print c
     EMPNO ENAME      JOB              MGR HIREDATE                   SAL       COMM     DEPTNO
      7369 SMITH      CLERK           7902 1980/12/17 00:00:00        800                    20
      7698 BLAKE      MANAGER         7839 1981/05/01 00:00:00       2850                    30
      7788 SCOTT      ANALYST         7566 1987/04/19 00:00:00       3000                    20
      7839 KING       PRESIDENT            1981/11/17 00:00:00       5000                    10
SQL>

How to make a bind variable out of a comparison like statement

I have a statement similar to the following -
select x from atable where acolumn like '1%';
How do I turn that into a variable in an anonymous block like -
declare
l_var varchar2(1) := '1';
begin
select x from atable where acolumn like 'l_var%'
end;
I need to prevent the database from using a literal in the plan so I need to convert like '%1' into a variable.
Any suggestions?

Not quite sure what you mean by 'binding' or 'substitution'.
If you mean bind variables, the yes oracle does automatically use bind variables:
SQL> CREATE TABLE atable
2 (
3          x VARCHAR2(10)
4 )
5 /
Table created.
SQL>
SQL> INSERT INTO atable VALUES ('1234');
1 row created.
SQL> COMMIT;
Commit complete.
SQL>
SQL> set serveroutput on size unlimited
SQL>
SQL> declare
2    l_var atable.x%TYPE := '1';
3    l_str atable.x%TYPE;
4 begin
5    select x
6      into l_str
7      from atable
8     where x like l_var || '%';
9
10    dbms_output.put_line ('l_str = "' || l_str || '"');
11 end;
12 /
l_str = "1234"
PL/SQL procedure successfully completed.
SQL>
SQL> SELECT SQL_TEXT FROM v$sql WHERE sql_text LIKE 'SELECT %ATABLE%' AND sql_text NOT LIKE '%V$SQL%';
SQL_TEXT
SELECT X FROM ATABLE WHERE X LIKE :B1 || '%'
SQL>Where that is the sql statement that the sql engine actually ran on behalf of the pl/sql routine.
GP>

How can i create "bind variable"

How can i create "bind variable" in my DB to support any procedure in my DB.
Thank you very much.

In SQL*PLUS we can defined bind variable
SQL>var x varchar2(250); -- Is x bind variable or i'm misunderstand ?
and ... in my procedure i can used ' &x ' to pass valued of 'x' from sql prompt to my procedure.
but i'm not sure variable x is still remain in DB because i need to pass variable
" v_stmt := 'and employee_id between ..... ' " from FORM to PROCEDURE in DB
how can i do

Using bind variables in Oracle SQL developer

Hi all,
i am using Oracle SQL developer. i want to use the bind variable in my sql.
variable myid number :=1;
select * from mds_3618_request where id = :myid;
but i am getting the below error.
Error starting at line 2 in command:
select * from mds_3618_request where id = :myid
Error report:
SQL Error: Missing IN or OUT parameter at index:: 1
Does Oracle SQL developer support bind variables in the SQL statements?
thanks in Advance
Vali Shaik

You are probable going to get a quicker answer on this forum : SQL Developer
-- Andy

Bind variables in SQL Developer

I declared a bind variable called 'test_num' and assigned a value of 10 as shown below.
variable test_num number
BEGIN
:test_num := 10;
dbms_output.put_line ('The Test Value: ' || :test_num);
END;
When I execute the above program, the output is thrown as 'The Test Value: '. The value of test_num is not shown. I fear whether this issue is due to SQL Developer which i am using to execute this program.
Please let me know why the value is not getting printed
Thanks for your help!

I see the same issue you are seeing when using the bind variable. The bind variable works fine in SQL*Plus but not from SQL Developer.
From SQLPlus*
SQL> set serveroutput on
SQL> variable test_num number
SQL> BEGIN
2 :test_num := 10;
3 dbms_output.put_line ('The Test Value: ' || :test_num);
4 END;
5 /
The Test Value: 10
PL/SQL procedure successfully completed.
From SQLDeveloper*
set serveroutput on
variable test_num number
BEGIN
:test_num := 10;
dbms_output.put_line ('The Test Value: ' || :test_num);
END;
anonymous block completed
The Test Value:

Prompt for bind variables in SQL developer

Hi!
Just installed the latest 3.2 version of SQL Developer, and tried to do an explain plan.
Now the tool prompts me for values for the bind variable. It didn't do that in my previous version (version 3. something).
Thats anoying :-)
How do I disable that feature?
Example:
explain plan for
select * from emp
where department_id = :1;
If i right click on the statement or press F10, I get no prompt for the bind variable...
Regards
Søren

Old fashioned way, like this:
EXPLAIN PLAN FOR
SELECT * FROM scott.emp
where deptno = :1;
SELECT PLAN_TABLE_OUTPUT FROM TABLE(DBMS_XPLAN.DISPLAY());
Executed with F5 gives me this output
plan FOR succeeded.
PLAN_TABLE_OUTPUT
Plan hash value: 3956160932
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 5 | 190 | 3 (0)| 00:00:01 |
|* 1 | TABLE ACCESS FULL| EMP | 5 | 190 | 3 (0)| 00:00:01 |
Predicate Information (identified by operation id):
1 - filter("DEPTNO"=TO_NUMBER(:1))
13 rows selected

How to catch possible bind variable performance impact during development?

Since producing load is a problem on development environment and the technics provided with Oracle can capture a parsing problem caused by a bind variable problem only after execution we are looking for pro-active solution like 10g compile time warnings stuff.
Using binds can have impact on indexed skewed data columns and paritioned tables, so lets just think about a typical oltp environment with always same access path results for similar queries using bind variables.
Using v$ views or even better dba_hist after 10g or 10046 trace are considered as re-active approaches since they can only be examined on a pre-production loaded environment.
Is there any tool or approach you are using or may suggest?
Thank you, best regards.
Tonguc

Are you using PL/SQL only?
If so, I'd look at all the EXECUTE IMMEDIATE's and DBMS_SQL calls throughout the code and determine one by one if they pose a threat. They should be rare, so a simple search against the USER_SOURCE could be sufficient.
Other programming languages will have different statements to watch out for.
I am not aware of any tool that does this for you.
Hope this helps.
Regards,
Rob.

EA3/EA2/EA1 - Bind Variables in PL/SQL

EA1 seems to have taken a backward step when it comes to supporting bind variables in PL/SQL.
Back in 1.1.3, according to the bugs fixed list, we apparently fixed bug 5884935 (BINDS IN A PL/SQL STATEMENT HAS "NOT ALL VARIABLES BOUND" ERROR), although this was only ever when running as scripts (as per Bind variables in PLSQL bug not fixed?
Now according to the 1.2 documentation, bind variables are not supported in the script runner (section 1.7.2) and the SQL*Plus variable command is not supported (section 1.7.1). However, I can run the following code "successfully" (no errors reported but the substitution text entered does not appear in the dbms_output):
variable bind_text varchar2(30);
declare
l_text varchar2(30);
begin
:bind_text := '&sub_text';
dbms_output.put_line('Bind text: "' || :bind_text || '"');
end;
Now in EA1, running this as a script results in "ORA-01006: bind variable does not exist"
Running the variable statement results in "ORA-00900: Invalid SQL Statement" and running the PL/SQL results in "ORA-1008: not all variables bound".
Can someone from the SQL Developer team please comment on the intended support for bind variables in PL/SQL?
Thanks,
theFurryOne

I know that the variable command isn't supported (as I said above), but that was also the case in 1.2, where it did actually sort of work.
I am not talking about local PL/SQL variables declared within the PL/SQL - I am trying to get user entered values into the PL/SQL in the same way as prompting for bind variable values in SQL.
So using SQL Developer bind variables inside PL/SQL is my end goal - preferably when running anonymous PL/SQL blocks as statements in the worksheet.
However, as there have been "fixed" bugs to enable bind variables in PL/SQL, which require the use of SQL Plus commands that are not supported in SQL Developer (ie variable), I am trying to work out what the development team think the intended support for bind variables in PL/SQL is. Then I will know if what I want needs to be reported as a bug or logged as an enhancement request.
theFurryOne

Using Bind variables in SQL PLUS Report

using Bind variables in SQL PLUS Report. This report gets the arguments from the application concurrent program. Now my need is to convert the start_date and end_date to bind Variables to improve the performance. I have commented the original code in 'prompt List of Unapproved Adjustments' and used my Bind Variable but it is giving an error
error: Bind Variable "ENDING_DATE" not declared
Report Date and Time:
26-OCT-2010 15:44:13
List of Unapproved Adjustments
Bind Variable 'ENDING_DATE" not declared
Please see below the code for the sql plus report:
define p_org_id = '&1'
define p_fy_begin_date = '&2'
define p_start_date = '&3'
define p_end_date = '&4'
define p_conversion = '&5'
declare
variable begin_date date;
exec :begin_date := p_start_date;
variable ending_date date;
exec :ending_date := p_end_date;
/* Begin
:begin_date := to_date('&p_start_date','YYYY/MM/DD HH24:MI:SS');
:ending_date := to_date('&p_end_date','YYYY/MM/DD HH24:MI:SS');
End; */
set newpage none
set termout off
set pagesize 55
set linesize 180
set heading on
set feedback off
set wrap off
set space 1
set heading on
begin
dbms_application_info.set_client_info('&p_org_id');
end;
prompt
prompt Report Date and Time:
prompt ----------------------
select to_char(sysdate,'DD-MON-YYYY HH24:MI:SS')
from dual ;
prompt
prompt List of Unapproved Adjustments
prompt -------------------------------
select b.trx_number,
a.adjustment_number,
f.user_name created_by
from apps.ar_adjustments a,
apps.ra_customer_trx b,
apps.fnd_user f
where a.customer_trx_id = b.customer_trx_id
and a.status <> 'A'
and a.created_by = f.user_id
and a.creation_date between :begin_date
and :ending_date
-- and a.creation_Date between to_date('&p_start_date','YYYY/MM/DD HH24:MI:SS')
-- and to_date('&p_end_date','YYYY/MM/DD HH24:MI:SS')
order by
b.trx_number ;

Hi
Please go to customization part of the report and verify..You have set a default value out there ..And also verify your lov and look at the values ..If it is again giving you the problem ..pl delete the report and develop it again from the scratch it will be solved...
vishnu
null

ADF BC / Why bind variables are mandatory in the sql query

I got this error during view object excecution in the component browser :
(oracle.jbo.SQLStmtException) JBO-27122: Erreur SQL lors de la préparation d'une instruction. Instruction : SELECT * FROM (Select distinct(socialgroup.socialgroup_i) from socialgroup, socialgroupmember, lodgingallocation, lodge
where socialgroup.socialgroup_i = socialgroupmember.socialgroup_i and socialgroupmember.t_socialgrouprole_i = t_rolegroup_ipar.fgetflextypologyclassitem_i(t_rolegroup_ipar.fisbeneficiary) and socialgroupmember.datefrom <= :DateTo and nvl(socialgroupmember.dateto, :DateFrom) >= :DateFrom and socialgroupmember.requester_i = lodgingallocation.requester_i and lodgingallocation.datefrom <= :DateTo and nvl(lodgingAllocation.DateTo, :DateFrom) >= :DateFrom and lodgingallocation.lodge_i = lodge.lodge_i) QRSLT ORDER BY "SOCIALGROUP_I"
----- LEVEL 1: DETAIL 0-----
(java.sql.SQLException) Tentative de définition d'un nom de paramètre qui ne se trouve pas dans le SQL: T_SICategory_I
The bind variables T_SICategory_I is not yet use in the sql query but will be used later so i defined it for the view object.
Is it a reason that the run time check this ? It would be more convenient to set the bind variables early when defining the view object and add them later during the development iteration.

Design-time defined named bind variables can be marked as required, or not.
This is decided by the use in the where clause or in view criteria. In my case the bind variable was not used in where clause neither in view criteria and that causes the error.
May be i would be nice to add a check box (a flag) that enable or disable the bind variables for this checking so we will be able to let it defined even we removed some part of the query corresponding to the corresponding restriction or we defined it earlier for a part of the query that is not yet defined.
In my current case i fully defined the bind variables but would refine my query later ... in that cause i would have to remove this bind variable and loose all the definitions to run this view object.
sorry for my english ...

[Solved] Named Bind Variables at Runtime - SQL WHERE clause issue

Hey 'all,
I've been having this issue today with a Search page using Named Bind Variables at Runtime for the search parameters for the WHERE clause in the view objects SQL.
I've got everything working except for a clearing method which I've created so that the user can clear the current WHERE clause from the SQL statment and set it as 1=2 (so that it doesn't do a blind query on load).
The method can clear and set the WHERE clause to 1=2 only when there is already one there.
Below are the methods: (located in my view object class)
public void findInvoiceById(Number invoiceId){
    setWhereClause("invoice_id = :P_INVOICE_ID");
    defineNamedWhereClauseParam("P_INVOICE_ID",null,null);
    setNamedWhereClauseParam("P_INVOICE_ID",invoiceId);
    executeQuery();
public void clearCriteria(){
    setWhereClause("1=2");
    removeNamedWhereClauseParam("P_INVOICE_ID");
    executeQuery();
}The error which I get is the following - this happens when the button is pressed twice in a row, or when no query has been passed previously.
1. JBO-29000: Unexpected exception caught: oracle.jbo.NoDefException, msg=JBO-25058: Definition P_INVOICE_ID of type Variable not found in SupplierInvoicesView1
2. JBO-25058: Definition P_INVOICE_ID of type Variable not found in SupplierInvoicesView1
Any help with this would be greatly appreciated!
Cheers,

Hi Bonnie,
we have it working ok, but still feel that there is room for improvement in the design.
For us the key factors are:
Pages based on the same view object that can be queried multiple ways.
We don't want to put design time bind variables in because it limits the use of the VO
We don't wan't multiple VO's with different where clauses.
The page is displaying the same table columns and fields, but the where clause must be dynamic.
We only want to query on the search field entered (some of our tables are massive)
TopLink named queries are really what we are after, but we don't want to forgo all the other ADF BC functionality. The only examples of ViewCriteria in the developer guide had literals in the where clause and no bind variables. The View Criteria may still be an option, but it appeared quite complex compaired to directly adding and removing bind variables at runtime.
a couple of footnotes:
the following methods are used to clear the runtime variables prior to reusing the VO (thanks to John Stegman for the pointer on the exception handler):
    public void clearBindVariable(String bindVariableName){
        try
            removeNamedWhereClauseParam(bindVariableName);
        catch (NoDefException e)
    public void clearBindVariables(){
        clearBindVariable("P_INVOICE_ID");
        clearBindVariable("P_INVOICE_NUM");
        clearBindVariable("P_SUPPLIER_NAME");
        clearBindVariable("P_INVOICE_DATE_FROM");
        clearBindVariable("P_INVOICE_DATE_TO");
        clearBindVariable("P_SUPPLIER_NUMBER");
    }We are using 1=1 and 1=2 in the where clause to supress blind querying. 1=2 is applied when ever we are not explicitely searching for something. We had a problem with using the refresh condition ${adfFacesContext.postback == true} which I posted about here:
executeQuery called twice using ${adfFacesContext.postback == true}
Would still gladly hear other ideas on a better reuse design.
regards,
Brenden

Why an "ORA-01006: bind variable does not exist" error when no dynamic SQL?

Hi all,
While running PL/SQL in SQL Developer 3.2.09, I got the following error after adding a section of code. Note that nothing I'm doing has anything to do with dynamic SQL (which is what 01006 is supposedly about).
Error report:
ORA-01006: bind variable does not exist
01006. 00000 - "bind variable does not exist"
*Cause:
*Action:
After commenting out the new chunk of code that caused the error, the error persisted.
After deleting the new code, the error went away.
What the heck!?!? If you have any ideas, please lay 'em on me.
Thanks so much,
Kim
P.S. It's a few hundred lines of code, so I didn't append it to this post and I don't see how to attach a file.

Let's review a few facts:
1. You post a question in the sql developer forum that has no apparent relation to sql developer. You could confirm this by doing the test using sql*plus or some other tool.
2. You provide NO information about what database you are even using. The only clue is an ORA -xxx message that means SOME version of Oracle is involved.
3. You provide NO information about what the four digit version of Oracle DB is being used.
4. You provide NO information about what the code in general or what that specific section of the code is even doing. The code could be doing literally anything that Oracle is capable of doing.
That's a bit like calling a mechanic you don't know, telling them your car is making a funny noise and asking them what the problem with your car is.
>
While running PL/SQL in SQL Developer 3.2.09, I got the following error after adding a section of code. Note that nothing I'm doing has anything to do with dynamic SQL (which is what 01006 is supposedly about).
Error report:
ORA-01006: bind variable does not exist
01006. 00000 - "bind variable does not exist"
*Cause:
*Action:
The error gives no indication of where the error occurred in the code.
>
Your first clue that your troubleshooting method is seriously flawed is when you make statements that aren't supported by any evidence at all but appear to be nothing but your opinion.
Your second clue is when those statements appear to directly contradict what Oracle is telling you.
I'm talking about these two statements you make; which you state as if they were universal truths
>
nothing I'm doing has anything to do with dynamic SQL
(which is what 01006 is supposedly about).
>
If thoe were true then your 'unstated' conclusion appears to be that Oracle is wrong in saying 'bind variable does not exist'
Sorry - but I would place my money on Oracle.
I'm sure the above may sound harsh - it is intended to be. My four major rules (there are more) when troubleshooting Oracle problems.
1. Assume that Oracle is CORRECT when it tells you there is a problem.
2. Assume that you are WRONG if your opinion conflicts with what Oracle is telling you - see rule #1.
3. Don't make ANY other assumptions. You can form hypotheses but don't state them as facts until they are proven.
4. Your 'opinion' is only useful to the extent that it can help you form meaningful hypotheses - see rule #3.
>
To reiterate, there is no dynamic SQL in the code.
>
To reiterate - if, as you state, that error relates to dynamic SQL and bind variables then it can not be disputed that:
ORACLE DOESN'T AGREE WITH YOU!
So let's try it my way and hypothesize that Oracle is correct (see rule #1 above).
Then by definition this statement by Oracle is correct
>
ORA-01006: bind variable does not exist
>
And that should immediately raise this question:
1. where might there be a bind variable that does not exist?
which leads to a prerequisite question:
2. where are ALL of the bind variables that might be being used?
Question #2 is where you need to start your search. Here are at least five possibilities (there are more)
1. your code - this should be easiest to check and you state that your 'anonymous' block does not have any.
2. a table trigger - triggers that use the :NEW, :OLD or :PARENT pseudocolumns. Those psuedocolumns are BIND variables and the trigger code that uses them is, by definition, dynamic sql.
3. a pl/sql package/function/procedure - any of these might be being called from trigger code or a view that is involved in the transaction. Any of these could take a parameter and/or use bind variables and cause your problem if that bind variable does 'not exist'.
4. a functional index - can also trigger code from #3 above
5. an audit trigger that logs the audit activity that your user or your code is performing. This code could be trying to use a SYS_CONTEXT environment variable that has not been created and cause a 'bind variable does not exist' error.
See rule #1 - Oracle is CORRECT. Until you have identified and examined ALL of the code (not just your anonymous block) being executed and ruled it out you should continue with the hypotheses that Oracle is CORRECT.
In the (extremely) unlikely event that you can show that Oracle is NOT correct you should file a SOR with Oracle.

Declare, Set, and Use a variable in a SQL Developer Query

I come from the SQL Server world and am trying to do something very simple: Declare, set, and use a variable in a query. For example:
Declare @lastPeriod date;
Set @lastPeriod = (select max(payperiod) from table 1 where payperiod < current_date);
Select field 1,
Field2
From table2
Where payperiod = @lastPeriod
The variable is going to be used in more areas in the query which is why I am simply not using a Sub-query in the where clause. I appreciate any assistance.

This forum is for issues with the SQL Developer tool. You'd get more response in the SQL And PL/SQL forum.
That said, read up on bind variables and substitution variables.
Whenever you can you should use Bind variables (e.g. *:lastPeriod* ), as they increase performance. In sqldev, there's no need to declare as you will be prompted to enter them on execution (F9), but you do if you execute as script (F5) (e.g. VARIABLE lastPeriod VARCHAR2(30);).
Alternatively, Substitution variables (e.g. *&lastPeriod* ) will literally be substituted in your statement before the database parses it. In sqldev, there's no need to declare as you will be prompted to enter them on execution (either F9 or F5), but you can (DEF lastPeriod='TEST'; ).
Have fun,
K.

Bind variables + SQL Developer

Similar Messages

Maybe you are looking for