Implement handling of triggers as separate database objects, on the same level as tables, routines and views. Means we have a trigger editor frame, a new icon and various code extensions. Fixes issue #806.

This commit is contained in:
Ansgar Becker
2009-12-11 16:07:59 +00:00
parent 6b92c3b08c
commit b4cca2ea1f
9 changed files with 480 additions and 14 deletions

View File

@ -15,7 +15,7 @@ uses Classes, SysUtils, Graphics, GraphUtil, db, clipbrd, dialogs,
type
TListNodeType = (lntNone, lntDb, lntTable, lntCrashedTable, lntView, lntFunction, lntProcedure, lntColumn);
TListNodeType = (lntNone, lntDb, lntTable, lntCrashedTable, lntView, lntFunction, lntProcedure, lntTrigger, lntColumn);
TListNodeTypes = Set of TListNodeType;
TListNode = record
Text: WideString;
@ -2194,7 +2194,9 @@ begin
else if t = 'FUNCTION' then
Result := lntFunction
else if t = 'PROCEDURE' then
Result := lntProcedure;
Result := lntProcedure
else if t = 'TRIGGER' then
Result := lntTrigger;
end else begin
if
TableStatus.IsNull(1) and // Engine column is NULL for views