It seems odd to me (and is causing me a little frustration) to insert a ; character before the SQL statement. What happens is I go to type in a new statement and forget that the previously autogenerated SQL doesn't end with one, then I get a syntax error and have to put one there myself.
I makes more sense, IMO, to end the statement with a ;. Is there a reason it is the way it is?
I guess consider this a feature request.