[11.5.355 Pro] - BUG: $COLUMNS$ with quoted pre/suffix

[11.5.355 Pro] - BUG: $COLUMNS$ with quoted pre/suffix

Using the $COLUMNS(...)$ macro with quoted prefix makes it go haywire. The snippet below

	Code:
	-- plain $COLUMNS(vertical,types)$ -- -------------------- -- prefix "DECLARE lv_"$COLUMNS(vertical,types)$ -- -------------------- -- suffix $COLUMNS(vertical,types)$";" -- -------------------- -- both "DECLARE lv_"$COLUMNS(vertical,types)$";" -- --------------------

yields the following code for a select few columns from a table:

Code:

-- plain
`cart_tid` int(10),
`tariff_zone_tid` int(10),
`user_profile_tid` int(10),
`line_tid` int(10)

-- --------------------
-- prefix
DECLARE lv_cart_tid_ int(10),
DECLARE lv_tariff_zone_tid_` int(10),
DECLARE lv_user_profile_tid_ int(10),
DECLARE lv_line_tid_ile_tid_ int(10)

-- --------------------
-- suffix
`cart_tid` int(10);,
`tariff_zone_tid` int(10);,
`user_profile_tid` int(10);,
`line_tid` int(10);

-- --------------------
-- both
DECLARE lv_cart_tid_ int(10);,
DECLARE lv_tariff_zone_tid_` int(10);,
DECLARE lv_user_profile_tid_ int(10);,
DECLARE lv_line_tid_ile_tid_ int(10);

-- --------------------

It's definitely the prefix that causes the problems, it garbles the names, and there's even a delimiter stuck in the middle of the second row between the column (the original name `tariff_zone_tid`) and its type that none of the other columns have.

Also, I recall using a suffix prevented the macro from adding the commas after each item which would make the result syntactically incorrect even if the prefix didn't slaughter the column names.

Thank you for letting us know. I have opened a defect for this issue with tracking number #SA0040050