Lines Matching refs:BEFORE

9258 **      CREATE TRIGGER trig BEFORE UPDATE ON t(a,b,c) ...;
9765 ** A trigger is either a BEFORE or an AFTER trigger.  The following constants
9768 ** If there are multiple triggers, you might of some BEFORE and some AFTER.
71136     ** used by any BEFORE and AFTER triggers that exist.  */
71146     /* Invoke BEFORE DELETE trigger programs. */
71152     ** the BEFORE triggers coded above have already removed the row
71184   /* Jump here if the row had already been deleted before any BEFORE
74791   /* Run the BEFORE and INSTEAD OF triggers, if there are any
74799     ** translated into a unique ID for the row.  But on a BEFORE trigger,
74854     /* Fire BEFORE or INSTEAD OF triggers */
83900         (tr_tm == TK_BEFORE)?"BEFORE":"AFTER", pTableName, 0);
83925   /* INSTEAD OF triggers can only appear on views and BEFORE triggers
83927   ** INSTEAD OF trigger into a BEFORE trigger.  It simplifies code
84546       (pTrigger->tr_tm==TRIGGER_BEFORE ? "BEFORE" : "AFTER"),
84676 ** BEFORE or AFTER triggers are coded. If the operation is an UPDATE, then
84769 ** and TRIGGER_AFTER bits set. Values accessed by BEFORE triggers are only
84927   int newmask;           /* Mask of NEW.* columns accessed by BEFORE triggers */
85220   ** If there are one or more BEFORE triggers, then do not populate the
85224   ** the database after the BEFORE triggers are fired anyway (as the trigger 
85240         ** into a register. This is done if there are no BEFORE triggers, or
85241         ** if there are one or more BEFORE triggers that use this value via
85252   /* Fire any BEFORE UPDATE triggers. This happens before constraints are
85264     ** is deleted or renamed by a BEFORE trigger - is left undefined in the
91651    26,  /*     BEFORE => ID */
91769   "ASC",           "ATTACH",        "BEFORE",        "BY",          
92105  /* 273 */ "trigger_time ::= BEFORE",
93807       case 273: /* trigger_time ::= BEFORE */
94482       testcase( i==8 ); /* BEFORE */