RE: Preventing ORA-1403 in triggers

From: Jesse, Rich <Rich.Jesse_at_qtiworld.com>
Date: Mon, 10 Dec 2001 14:04:40 -0800
Message-ID: <F001.003D951C.20011210135020@fatcity.com>

Thanks guys!

I'm thinking that we're going to use the anonymous block local exception idea. Now if they would let me turn this mess into a materialized view, my question would be moot!

Thanks again!

Rich Jesse                          System/Database Administrator
Rich.Jesse_at_qtiworld.com             Quad/Tech International, Sussex, WI USA

----------------

Hi,

So a developer asks me "How do I prevent ORA-1403 in my SELECT statement in my trigger?" I thought this would be simple, but my brain's just not all here.

The statement is simple:

        SELECT description INTO v_desc
        FROM    mytable
        WHERE   indexcol1 = :v_col1
                AND indexcol2 = :v_col2

The problem is that we don't know if the user-entered "indexcol"s exist. I could preface this statement with a "SELECT count(*) INTO mycount..." to see if there are existing rows, but I was hoping to do this all in one SQL statement if possible, especially if/when this scenarios will happen with non-indexed columns (don't ask).
--

Please see the official ORACLE-L FAQ: http://www.orafaq.com
--

Author: Jesse, Rich
  INET: Rich.Jesse_at_qtiworld.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------

To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Mon Dec 10 2001 - 16:04:40 CST