Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Reading the docs, it seems like it's just for creating the triggers, not executing them.

    • Sorry, but not quite correct. It's a pain to read through, but this is the killer:

      At trigger activation time, privileges are checked against the DEFINER user. This user must have these privileges:

      • The TRIGGER privilege. (SUPER prior to MySQL 5.1.6.)
      • The SELECT privilege for the subject table if references to table columns occur via OLD.col_name or NEW.col_name in the trigger definition.
      • The UPDATE privilege for the subject table if table columns are targets of SET NEW.col_name = value assignments in the trigger definition.
      • Whatever other privileges normally are required for the statements executed by the trigger.

      That was not fun to track down, but there ya go.

      • Ugh, MySQL is _so_ lame.

      • Have you tested that? .. as it still seems to apply the privilege tests to the user that defined the trigger, rather than the user invoking it.

        --

        @JAPH = qw(Hacker Perl Another Just);
        print reverse @JAPH;
      • Like Teejay said, DEFINER

        Are you seeing something we're missing?