[SA 7.1.228 Pro] - Funny glitch with braces

[SA 7.1.228 Pro] - Funny glitch with braces

I ran into a funny glitch with braces today. I have a snippet that I wanted to edit and dropped its content into SQL Editor to sort out the required number of braces.

	Code:
	DECLARE EXIT HANDLER FOR SQLEXCEPTION BEGIN ROLLBACK; INSERT INTO ertekesites.error_log(error_msg) VALUES (CONCAT(TRIM(TRAILING ', ' FROM CONCAT('/Failed statement:/ CALL $OBJECT(ins_qualname, proc)$(', "COALESCE("$ARGS$", 'NULL'),', '")),');')); SELECT @id_error_log := LAST_INSERT_ID(); END;

The Jump to Matching Brace function does not work very well with this one. It's not supposed to happen very often but this time it was deeply misleading :) I'm not sure this one should (or could easily) be fixed, though.

I don't think this is a bug. The code here is very snippet-syntax specific, that piece "COALESCE("$ARGS$", 'NULL'),', '" of code is not a valid SQL code, it converts to a valid code only after the snippet code execution. The SQL parser chokes on that and it fails to match brackets correctly in the present format.

Last edited by SysOp on Mon Dec 01, 2014 9:23 am; edited 1 time in total

	SysOp wrote:
	I don't think this is a bug. The code here is very snippet-syntax specific, that piece "COALESCE("$ARGS$", 'NULL'),', '" of code is not a valid SQL code, it converts to a valid code only after the snippet code execution. The SQL parser chokes on that and it fails to match brackets correctly in the present format.

Neither do I. That's why I said it was just a glitch and that I wasn't sure it should be fixed. It's just a funny anomaly.