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

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&gt;

Value of orders_seq.nextval = 1000

PL/SQL-procedure is geslaagd.

This entry was posted by Jurgen Kemmelings on July 13, 2007 at 11:00 am, and is filed under General. Follow any responses to this post through RSS 2.0.Both comments and pings are currently closed.

Comments (4)
Related Posts

Comments are closed
#1 written by Asif Momen 5 years ago

Hi,

Karl is right. Oracle internally converts the assignment into equivalent SQL statement. Click here, to have a look at the test.
#2 written by Asif Momen 5 years ago

Hi,

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

Momen
#3 written by Karl 5 years ago

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 written by Patrick Sinke 5 years ago

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.
Comment Feed for this Post