New PL/SQL Feature in Oracle 11g: the use of sequence.nextval 13422386 1019544571447648 7687716130941590224 o1

New PL/SQL Feature in Oracle 11g: the use of sequence.nextval

July 13, 2007 IT 4 Comments

Another small new feature in Oracle 11g PL/SQL: you can directly use sequence.nextval (and sequence.currval). It is not necessary anymore to do something like select sequence.nextval into l_seq from dual in your PL/SQL block. A small example: 

declare
  l_seq number;
begin
  l_seq := oe.orders_seq.nextval;
  dbms_output.put_line('Value of orders_seq.nextval = '||to_char(l_seq));
end;

SQL>

Value of orders_seq.nextval = 1000

PL/SQL-procedure is geslaagd.

Related Posts

About The Author

Jurgen Kemmelings

Oracle consultant at AMIS

4 Comments

  1. Asif Momen September 25, 2007

    Hi,

    Karl is right. Oracle internally converts the assignment into equivalent SQL statement. Click here, to have a look at the test.

  2. Asif Momen September 24, 2007

    Hi,

    Karl is right. Oracle internally translates the assignment into equivalent SQL statement. Read this for a test case.

    Momen

  3. Karl July 19, 2007

    Hi,
    i assume that ‘l_seq := oe.orders_seq.nextval;’ is translated/executed internally to ‘SELECT oe.orders_seq.nextval INTO l_seq FROM DUAL;’
    did you trace it?

    Karl

  4. Patrick Sinke July 13, 2007

    This is another small but good step in the right direction. I tried if it was possible to assign a sequence to the default expression of a column, but it appears this feature is really restricted to PL/SQL.
    As I see it now, many features are small tweaks to pl/sql.