Event-Editor bug on timing end date "no end date"

[MarkBrock]

In the new version 3.10.205 there is a bug in the event editor, when selecting "no end date" in the timing tab.
The SQL Statement is displayed and executed as follows:
...
ON SCHEDULE EVERY '1' MONTH
STARTS '2009-01-01 00:00:00'
ENDS CURRENT_TIMESTAMP
ON COMPLETION PRESERVE
DO
...
This cause an error "ENDS is either invalid or before STARTS"
I think the ends clause must be removed in the SQL when selecting no end date.

[Alexz]

We'll work over this problem. The fix will be available in the next build of dbForge for MySQL.

[MarkBrock]

thx