blocks|key|1706355|text|是的，该异常除了引发相同的错误外，什么也不做。此外，它还用于屏蔽错误的实际行号。如果我是你的话我会把它去掉。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1706356|例如：|1706357|SQL>+declare
++2++++v+number;
++3++begin
++4++++select+1+into+v+from+dual;
++5++++select+'a'+into+v+from+dual;
++6++exception
++7++++when+others
++8++++then
++9++++++raise;
+10++end;
+11++/
declare
*
ERROR+at+line+1:
ORA-06502:+PL/SQL:+numeric+or+value+error:+character+to+number+conversion+error
ORA-06512:+at+line+9|code-block|syntax|javascript|1706358|vs：|1706359|SQL>+declare
++2++++v+number;
++3++begin
++4++++select+1+into+v+from+dual;
++5++++select+'a'+into+v+from+dual;
++6++end;
++7++/
declare
*
ERROR+at+line+1:
ORA-06502:+PL/SQL:+numeric+or+value+error:+character+to+number+conversion+error
ORA-06512:+at+line+5|1706360|第一行中的行号指向raise，而不是实际的行号。这会使追踪错误变得更加困难。|1706361|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

yes, that exception does nothing but raise the same error out. also it serves to mask the real line number of the error. i'd remove that if I were you.

eg:

<pre><code>SQL&gt; declare
 2 v number;
 3 begin
 4 select 1 into v from dual;
 5 select 'a' into v from dual;
 6 exception
 7 when others
 8 then
 9 raise;
 10 end;
 11 /
declare
*
ERROR at line 1:
ORA-06502: PL/SQL: numeric or value error: character to number conversion error
ORA-06512: at line 9
</code></pre>

vs:

<pre><code>SQL&gt; declare
 2 v number;
 3 begin
 4 select 1 into v from dual;
 5 select 'a' into v from dual;
 6 end;
 7 /
declare
*
ERROR at line 1:
ORA-06502: PL/SQL: numeric or value error: character to number conversion error
ORA-06512: at line 5
</code></pre>

the line number in the first one is pointing to the raise instead of the real line number. it can make tracking down errors harder.

blocks|key|1706465|text|它不仅仅是什么都不做，它近乎犯罪。它基本上是这样说的：“只是为了好玩，我将假装错误发生在此行，而不是真正的行。”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1706466|异常处理是整个语言中最容易被误解的方面。上面的情况很常见，我认为它源于一种基本的误解，即“未处理的异常”是一件坏事(它几乎回避了一个问题--为什么你没有处理它？)如果Oracle使用了“发生异常”或“遇到异常”这样的术语，我们这些必须支持此代码的穷人就会少得多“当其他人”的异常处理程序让我们的生活苦不堪言。|1706467|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

It doesn't just do nothing at all, it is verging on criminal. It basically says "Just for fun, I'm going to pretend that the error occurred at this line rather than the real line."

Exception handling is the most misunderstood aspect of the entire language. The above is very common, and I think it stems from the basic misconception that an 'unhandled exception' is a bad thing (it almost begs the question - why didn't you handle it?). If only Oracle had used the terminology 'exception occured' or 'exception encountered', us poor folks who have to support this code would have far fewer 'WHEN OTHERS' exception handlers making our lives miserable.

blocks|key|1920010|text|它除了屏蔽错误行之外什么也不做，就像@DazzaL点一样。但它起到了提醒的作用，告诉您上面的代码可以引发应该处理的异常，但处理方式仍然是未定义的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1920011|在其他编程语言中，您可以自动创建try/catch块(例如，在Eclipse/Java、Netbeans/PHP或Visual+Studio/C#中)，并且它是使用catch创建的(就像“当其他人”一样)，其中默认行为是再次抛出异常，而程序员决定当异常引发时应该做什么。|1920012|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

It does nothing at all but mask error line, as @DazzaL points. But it serves as a reminder, telling you that the code above can raise an exception that should be treated but treatment remains undefined.

In other programming languages you can create a try/catch block automatically (e.g. in Eclipse/Java, Netbeans/PHP or Visual Studio/C#), and it is created with a catch (like the "when others") wich default behaviour is throw again the exception, while programmer decide what should be done when an exception is raised.

Being still a newbie in PL/SQL, I've been copying and pasting around the following trigger:

<pre><code>CREATE OR REPLACE TRIGGER FOO_TRG1
 BEFORE INSERT
 ON FOO
 REFERENCING NEW AS NEW OLD AS OLD
 FOR EACH ROW
BEGIN
 IF :NEW.FOO_ID IS NULL THEN
 SELECT FOO_SEQ1.NEXTVAL INTO :NEW.FOO_ID FROM DUAL;
 END IF;

 EXCEPTION
 WHEN OTHERS THEN RAISE;
END FOO_TRG1;
/
ALTER TRIGGER FOO_TRG1 ENABLE;
</code></pre>

I suspect that the included exception handling code does nothing at all and could simply get removed, since I'll get an error message anyway if something goes wrong. Am I right?

(I guess such code is the result of further editing prior code.)

Does `EXCEPTION WHEN OTHERS THEN RAISE` do something?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

作为PL/SQL的新手，我一直在复制和粘贴以下触发器：CREATE OR REPLACE TRIGGER FOO_TRG1    BEFORE INSERT    ON FOO    REFERENCING NEW AS NEW OLD AS OLD    FOR EACH ROWBEGIN    IF :NEW.FO...

问当其他人做某事时，“`EXCEPTION `EXCEPTION RAISE`”会做些什么吗？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问当其他人做某事时，“`EXCEPTION `EXCEPTION RAISE`”会做些什么吗？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问当其他人做某事时，“`EXCEPTION `EXCEPTION RAISE`”会做些什么吗？
EN