| Bug #45929 | Trigger editor - auto delimiter is very ennoying | ||
|---|---|---|---|
| Submitted: | 3 Jul 2009 5:48 | Modified: | 4 Nov 2009 17:10 |
| Reporter: | Petr Burian | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
| Version: | 5.1.16 | OS: | Any |
| Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
| Tags: | DELIMITER, trigger, TTREV | ||
[3 Jul 2009 5:50]
Petr Burian
Easy schema to reproduce bug
Attachment: relation.mwb (application/octet-stream, text), 5.96 KiB.
[3 Jul 2009 7:13]
Valeriy Kravchuk
Thank you for the problem report. Verified just as described on Windows XP.
[29 Oct 2009 4:21]
Alfredo Kojima
This has been fixed.
[3 Nov 2009 16:25]
Johannes Taxacher
this has been fixed in 5.1.18 and 5.2.6. while WB still adds the closing delimiter, theres no repositioning of the cursor anymore and the delimiter is added (if needed) at the very end of the code
[4 Nov 2009 17:10]
Tony Bedford
An entry was added to the 5.1.18 and 5.2.6 changelogs: When editing a trigger, the trigger editor would automatically insert a delimiter during a pause in typing, and also relocate the cursor.
Description: Create new schema, and put 3 tables 'main', 'table_a', 'table_b'. Open table 'table_a' and create trigger. While writing trigger with some pauses (to think about what I am writing) there is still delimiter '//' automaticly placed. This is annoying because: * I have to delete it every time I want continue * Cursor is places between delimiter '/cursor/' whenever I pause after word and make a space ('CREATE TRIGGER test AFTER ' - see the last space - became 'CREATE TRIGGER test AFTER/cursor/') I think editor should leave delimiter placement on user or at least disable this feature in setup. How to repeat: See Description