You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello
I found, postgresql highlighter seems to be lost when a source code contains anonymous code block.
Such block can be defined by following constructs
DO $$
BEGIN
-- some code
END
$$ LANGUAGE plpgsql;
or
DO LANGUAGE plpgsql $$
BEGIN
END $$;
Other languages than plpgsql (like python etc) doen't require BEGIN-END commands.
In current version of highlighter any code existing after anonymous code block is treated as a comment (at least judging by colours). On the other side, SQLServer highlighter behaves properly.
Hello
I found, postgresql highlighter seems to be lost when a source code contains anonymous code block.
Such block can be defined by following constructs
or
Other languages than plpgsql (like python etc) doen't require BEGIN-END commands.
In current version of highlighter any code existing after anonymous code block is treated as a comment (at least judging by colours). On the other side, SQLServer highlighter behaves properly.
Tested at: https://ace.c9.io/build/kitchen-sink.html
With regards
The text was updated successfully, but these errors were encountered: