| Bug #12321 | information_schema.TRIGGERS.ACTION_STATEMENT misses one space | ||
|---|---|---|---|
| Submitted: | 2 Aug 2005 15:49 | Modified: | 2 Aug 2005 21:56 |
| Reporter: | MySQL-Front Team | Email Updates: | |
| Status: | Not a Bug | Impact on me: | |
| Category: | MySQL Server | Severity: | S3 (Non-critical) |
| Version: | 5.0.10a-beta | OS: | Windows (Windows XP) |
| Assigned to: | CPU Architecture: | Any | |
[2 Aug 2005 21:56]
MySQL-Front Team
Sorry, my mistake. All is fine!
[27 Aug 2005 12:25]
MySQL-Front Team
Hm, right now I think again this is a bug: In information_schema.TRIGGERS.ACTION_STATEMENT there should not be a starting space. This starting space is only the separator from the trigger header and the trigger statement. But this separator is not a part of the statement - like reported in "ACTION_STATEMENT". Please feel free to fix this bug or let them existing. Since I know this bug I know how to handle them. Or with other words: This bug report is a present to you to help you. This is not any kind of request about fixing anything. Please let me know, if you are interessed to get presents like this or if you prefer not to know you bugs.
Description: information_schema.TRIGGERS.ACTION_STATEMENT shows something like this: BEGIN INSERT INTO test2 SET a2 = NEW.a1; DELETE FROM test3 WHERE a3 = NEW.a1; UPDATE test4 SET b4 = b4 + 1 WHERE a4 = NEW.a1; END Like you can see there is only one space before the starting BEGIN. This looks like a bug... How to repeat: SELECT ACTION_STATEMENT FROM information_schema.TRIGGERS;