SQL> BEGIN 2 DBMS_OUTPUT.PUT_LINE('Nextval=' || TO_CHAR(s.NEXTVAL)) 3 END 4 / The sequence pseudo-columns can be referenced directly, which means that we can bypass the intermediate variable assignment if necessary, as follows. Nextval=2PL/SQL procedure successfully completed. SQL> DECLARE 2 n PLS_INTEGER := s.NEXTVAL 3 BEGIN 4 DBMS_OUTPUT.PUT_LINE('Nextval=' || TO_CHAR(n)) 5 END 6 / We can also use the sequence expression to set a default for our variable, as the following example demonstrates. Nextval=1PL/SQL procedure successfully completed. SQL> DECLARE 2 n PLS_INTEGER 3 BEGIN 4 n := s.NEXTVAL 5 DBMS_OUTPUT.PUT_LINE('Nextval=' || TO_CHAR(n)) 6 END 7 / In our first example, we will assign the NEXTVAL pseudo-column to a variable, as follows. To demonstrate this, we will create a sequence ('S') and run some simple examples, as follows.

This means we can use sequence expressions in PL/SQL anywhere we can validly use a number. In 11g, however, Oracle has added sequence fetching (using NEXTVAL and CURRVAL) to the list of valid PL/SQL expressions. retrieving NEXTVAL or CURRVAL) is a SQL-only operation (we typically use a DUAL construct). In versions prior to 11g, assigning a variable from a sequence (i.e. As most developers will be aware, sequences have never been directly supported in PL/SQL. We will begin with Oracle 11g's support for sequence expressions in PL/SQL.

Oracle has also included several smaller PL/SQL enhancements and the following features are briefly covered in this article: Oracle has released some major new features for PL/SQL developers with 11g (see this list of articles for details).

Pl sql developer 11