DELIMITER $$
-- before inserting new id
DROP TRIGGER IF EXISTS before_insert_id$$
CREATE TRIGGER before_insert_id
BEFORE INSERT ON test FOR EACH ROW
BEGIN
-- condition to check
IF NEW.id < 0 THEN
-- hack to solve absence of SIGNAL/prepared statements in triggers
UPDATE `Error: invalid_id_test` SET x=1;
END IF;
END$$
DELIMITER ;
DELIMITER $$
-- my_signal procedure
CREATE PROCEDURE `my_signal`(in_errortext VARCHAR(255))
BEGIN
SET @sql=CONCAT('UPDATE `', in_errortext, '` SET x=1');
PREPARE my_signal_stmt FROM @sql;
EXECUTE my_signal_stmt;
DEALLOCATE PREPARE my_signal_stmt;
END$$
CREATE PROCEDURE insert_test(p_id INT)
BEGIN
IF NEW.id < 0 THEN
CALL my_signal('Error: invalid_id_test; Id must be a positive integer');
ELSE
INSERT INTO test (id) VALUES (p_id);
END IF;
END$$
DELIMITER ;
signal sqlstate '45000' set message_text = 'My Error Message';
状态45000是表示“未处理的用户定义异常”的通用状态。 下面是一个更完整的方法示例:
delimiter //
use test//
create table trigger_test
(
id int not null
)//
drop trigger if exists trg_trigger_test_ins //
create trigger trg_trigger_test_ins before insert on trigger_test
for each row
begin
declare msg varchar(128);
if new.id < 0 then
set msg = concat('MyTriggerError: Trying to insert a negative value in trigger_test: ', cast(new.id as char));
signal sqlstate '45000' set message_text = msg;
end if;
end
//
delimiter ;
-- run the following as seperate statements:
insert into trigger_test values (1), (-1), (2); -- everything fails as one row is bad
select * from trigger_test;
insert into trigger_test values (1); -- succeeds as expected
insert into trigger_test values (-1); -- fails as expected
select * from trigger_test;
DELIMITER @@
DROP TRIGGER IF EXISTS trigger_name @@
CREATE TRIGGER trigger_name
BEFORE UPDATE ON table_name
FOR EACH ROW
BEGIN
--the condition of error is:
--if NEW update value of the attribute age = 1 and OLD value was 0
--key word OLD and NEW let you distinguish between the old and new value of an attribute
IF (NEW.state = 1 AND OLD.state = 0) THEN
signal sqlstate '-20000' set message_text = 'hey it's an error!';
END IF;
END @@
DELIMITER ;
CREATE TRIGGER sample_trigger_msg
BEFORE INSERT
FOR EACH ROW
BEGIN
IF(NEW.important_value) < (1*2) THEN
DECLARE dummy INT;
SELECT
Enter your Message Here!!!
INTO dummy
FROM mytable
WHERE mytable.id=new.id
END IF;
END;
BEGIN
-- Force one of the following to be assigned otherwise set required field to null which will throw an error
IF (NEW.`nullable_field_1` IS NULL AND NEW.`nullable_field_2` IS NULL) THEN
SET NEW.`required_id_field`=NULL;
END IF;
END
如果您使用的是5.5+,则可以使用其他答案中描述的信号状态:
BEGIN
-- Force one of the following to be assigned otherwise use signal sqlstate to throw a unique error
IF (NEW.`nullable_field_1` IS NULL AND NEW.`nullable_field_2` IS NULL) THEN
SIGNAL SQLSTATE '45000' set message_text='A unique identifier for nullable_field_1 OR nullable_field_2 is required!';
END IF;
END
7条答案
按热度按时间jdzmm42g1#
不幸的是,@ruidc提供的答案在5.5之前的mysql版本中不起作用,因为没有为存储过程实现signal。
我找到的解决方案是模拟一个信号
table_name doesn't exist
错误,将自定义错误消息推入table_name
.黑客可以使用触发器或存储过程来实现。下面我将按照@ruidc使用的示例来描述这两个选项。
使用触发器
使用存储过程
存储过程允许您使用动态sql,这使得在一个过程中封装错误生成功能成为可能。相反,我们应该控制应用程序的insert/update方法,因此它们只使用我们的存储过程(不授予插入/更新的直接权限)。
tzdcorbm2#
从MySQL5.5开始,您可以使用
SIGNAL
引发异常的语法:状态45000是表示“未处理的用户定义异常”的通用状态。
下面是一个更完整的方法示例:
mitkmikd3#
以下过程是(在mysql5上)抛出自定义错误并同时记录它们的一种方法:
at0kjp5o4#
这里有一个黑客可能会工作。它不干净,但看起来可能有用:
实际上,您只是尝试更新一个不存在的列。
9jyewag05#
jhdbpxl96#
yhxst69z7#
您可以使用的另一种(黑客)方法(如果您出于某种原因未使用5.5+):
如果您有一个必填字段,那么在触发器中,将必填字段设置为无效值,如null。这将适用于insert和update。请注意,如果null是必填字段的有效值(出于某些疯狂的原因),那么这种方法将不起作用。
如果您使用的是5.5+,则可以使用其他答案中描述的信号状态: