We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Submitted by: @asfernandes
Before Firebird 3.0, the table name was ignored when changed from the original trigger in a CREATE OR ALTER TRIGGER.
In Firebird 3.0, it started to change the trigger's table.
Test case:
recreate table t1 (n integer); recreate table t2 (n integer);
create or alter trigger trig1 before insert on t1 as begin end; show trigger trig1; -- table: t1
create or alter trigger trig1 after insert on t2 as begin end; show trigger trig1; -- table: t2
The text was updated successfully, but these errors were encountered:
assignee: Adriano dos Santos Fernandes [ asfernandes ]
Sorry, something went wrong.
Commented by: @mrotteveel
Sounds like expected behavior to me, why'd you want to revert this?
Commented by: @asfernandes
I was thinking it was an unintentionally and incomplete change, but it's not, and it's working.
It was done in CORE4846 by me :D
status: Open [ 1 ] => Resolved [ 5 ]
resolution: Won't Fix [ 2 ]
status: Resolved [ 5 ] => Closed [ 6 ]
asfernandes
No branches or pull requests
Submitted by: @asfernandes
Before Firebird 3.0, the table name was ignored when changed from the original trigger in a CREATE OR ALTER TRIGGER.
In Firebird 3.0, it started to change the trigger's table.
Test case:
recreate table t1 (n integer);
recreate table t2 (n integer);
create or alter trigger trig1 before insert on t1 as begin end;
show trigger trig1;
-- table: t1
create or alter trigger trig1 after insert on t2 as begin end;
show trigger trig1;
-- table: t2
The text was updated successfully, but these errors were encountered: