插入后删除触发器

Question

I have two tables, new table and registered table, what I want is that what is new will be registered when an update is made to a boolean (Accepted = 1 send it to registered) and after the information has been inserted back to registered delete that same one again, try to make a trigger that would do that but although it saves me well when doing this operation the trigger does not advance and does not do the operations

BEGIN
CREATE TRIGGER `trigger_1` AFTER UPDATE ON `new` 
FOR EACH ROW INSERT INTO registered (Num_Registered, Name_Registered, Type_Id, Semes_Registered, Fac_Registered, Pass) SELECT Mat_New, Name_New, Id_New, Semes_New, Fac_New, Pass_New FROM new WHERE Accepted=1;

DELETE FROM new WHERE Accepted=1 OR Accepted=0;//Here taking into account that 0 is rejected and deleted, and 1 is accepted and sent to registered
END;

In the same way I tried to make 2 triggers (one that made the insertion of one table to another and then another trigger that after the insertion deletes said in the table first) but they only collide with each other * error 1442 -cant update table new in stored function / trigger because it is already in use by statement which invoked this stored function / trigger

CREATE TRIGGER `trigger_1` BEFORE UPDATE ON `new`
FOR EACH ROW INSERT INTO registered (Num_Registered, Name_Registered, Type_Id, Semes_Registered, Fac_Registered, Pass) SELECT Mat_New, Name_New, Id_New, Semes_New, Fac_New, Pass_New FROM new WHERE Accepted=1;


CREATE TRIGGER `trigger_2` AFTER UPDATE ON `new`
 FOR EACH ROW DELETE FROM new WHERE Accepted=1 OR Accepted=0;//Here taking into account that 0 is rejected and deleted, and 1 is accepted and sent to registered

Answer 1

Obviously, the insert into the registrations table is simple. And I can understand reasons why you would want this. For instance, you might have additional data for the "accepted" folks. You might want foreign key relationships only to "accepted".

The challenge is that you want the update to turn into a delete . I don't think that is possible in a trigger in MySQL. But a simple alternative is to just use a view:

create view v_new as
    select n.*
    from new n
    where n.accepted <> 1;

This also has the advantage that you have a record of everyone who was ever new, even though they would not be visible to the users who use the view.