Skip site navigation (1) Skip section navigation (2)

Re: Anybody have an Oracle PL/SQL reference at hand?

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Anybody have an Oracle PL/SQL reference at hand?
Date: 2004-07-31 19:13:24
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Hi Tom,

I have sent you and the list the HTML page from the oracle tech network 
describing all of this.  However, it seems to have disappeared in to the 
void since you don't seem to have received it and it hasn't hit the list 

You can get a free login to access all the oracle docs and manuals, here:

If you like, however, I can just zip and email you the full PL/SQL PDF 
manual that I just downloaded from the above URL.

Let me know if you want the PDF emailed to you.

> Can anyone check how well the syntax of plpgsql EXCEPTION, as described
> at
> agrees with what Oracle does?  I did some googling but couldn't find
> anything that seemed authoritative.  I'm wondering in particular if
> Oracle allows multiple condition names per WHEN, along the lines of
> 	WHEN condition [ , condition ... ] THEN
> 		handler_statements

It does, but with a different syntax:

If you want two or more exceptions to execute the same sequence of 
statements, list the exception names in the WHEN clause, separating them 
by the keyword OR, as follows:

    WHEN over_limit OR under_limit OR VALUE_ERROR THEN
       -- handle the error

If any of the exceptions in the list is raised, the associated sequence 
of statements is executed. The keyword OTHERS cannot appear in the list 
of exception names; it must appear by itself. You can have any number of 
exception handlers, and each handler can associate a list of exceptions 
with a sequence of statements. However, an exception name can appear 
only once in the exception-handling part of a PL/SQL block or subprogram.

> Also it would be nice to see a complete list of the "condition" names
> that they accept.  I whipped up a quick table based on our ERRCODE
> macro names, see
> but I'm certain that's not what we really want to expose to users
> in the long run.

  	A program attempts to assign values to the attributes of an 
uninitialized object.

  	None of the choices in the WHEN clauses of a CASE statement is 
selected, and there is no ELSE clause.

  	A program attempts to apply collection methods other than EXISTS to 
an uninitialized nested table or varray, or the program attempts to 
assign values to the elements of an uninitialized nested table or varray.

  	A program attempts to open an already open cursor. A cursor must be 
closed before it can be reopened. A cursor FOR loop automatically opens 
the cursor to which it refers, so your program cannot open that cursor 
inside the loop.

  	A program attempts to store duplicate values in a database column 
that is constrained by a unique index.

  	A program attempts a cursor operation that is not allowed, such as 
closing an unopened cursor.

  	In a SQL statement, the conversion of a character string into a 
number fails because the string does not represent a valid number. (In 
procedural statements, VALUE_ERROR is raised.) This exception is also 
raised when the LIMIT-clause expression in a bulk FETCH statement does 
not evaluate to a positive number.

  	A program attempts to log on to Oracle with an invalid username or 

  	A SELECT INTO statement returns no rows, or your program references a 
deleted element in a nested table or an uninitialized element in an 
index-by table. Because this exception is used internally by some SQL 
functions to signal that they are finished, you should not rely on this 
exception being propagated if you raise it within a function that is 
called as part of a query.

  	A program issues a database call without being connected to Oracle.

  	PL/SQL has an internal problem.

  	The host cursor variable and PL/SQL cursor variable involved in an 
assignment have incompatible return types. For example, when an open 
host cursor variable is passed to a stored subprogram, the return types 
of the actual and formal parameters must be compatible.

  	A program attempts to call a MEMBER method, but the instance of the 
object type has not been initialized. The built-in parameter SELF points 
to the object, and is always the first parameter passed to a MEMBER method.

  	PL/SQL runs out of memory or memory has been corrupted.

  	A program references a nested table or varray element using an index 
number larger than the number of elements in the collection.

  	A program references a nested table or varray element using an index 
number (-1 for example) that is outside the legal range.

  	The conversion of a character string into a universal rowid fails 
because the character string does not represent a valid rowid.

  	A time-out occurs while Oracle is waiting for a resource.

  	A SELECT INTO statement returns more than one row.

  	An arithmetic, conversion, truncation, or size-constraint error 
occurs. For example, when your program selects a column value into a 
character variable, if the value is longer than the declared length of 
the variable, PL/SQL aborts the assignment and raises VALUE_ERROR. In 
procedural statements, VALUE_ERROR is raised if the conversion of a 
character string into a number fails. (In SQL statements, INVALID_NUMBER 
is raised.)

  	A program attempts to divide a number by zero.


In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2004-07-31 19:28:06
Subject: Re: plpgsql compile error on win32
Previous:From: Magnus HaganderDate: 2004-07-31 18:20:53
Subject: Re: plpgsql compile error on win32

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group