[12.1.279 Pro] - BUG: Refactoring variable and delimiters

[12.1.279 Pro] - BUG: Refactoring variable and delimiters

When trying to refactor part of the code into a stored procedure the process uses a macro called $REFACTORING_OBJ_NAME$. That macro obeys the Always Add Delimiters only half-heartedly. The schema part gets delimited, but the object part does not. Check this short video here.

It is not shown in the video but I tinkered further with it and it turned out that the object name only gets delimited if it contains a character that requires it to be delimited, eg. a space or a dash. In these cases, the delimiters are added, entering the following as the Procedure Name:

	Code:
	part1.part2 part3 becomes [part1].[part2 part3] part1.part2-part3 becomes [part1].[part2-part3]

If I add a period, the whole object chain gets shifted out to the left, entering the following as the Procedure Name:

	Code:
	part1.part2 becomes [part1].part2 part1.part2.part3 becomes [part2].part3 etc.

If I want to add a period to the name, I have to add the delimiter to the Procedure Name manually, so entering this works properly:

	Code:
	part1.[part2.part3]

However, manually adding the delimiters to a name that would otherwise not require it does not work at all, the delimiters get stripped, yielding funny results like:

	Code:
	part1.[part2] becomes [part1].part2

I'm afraid the $REFACTORING...$ macros haven't been designed to follow the Delimiters settings. It could be an oversight, I'm not sure.

That explains it then. Thanks for the info!

I've been told the refactoring macros were introduced before the global option for controlling delimiters became available, and indeed, it's an oversight they didn't get updated at that time. I submitted a ticket to get that rectified.

Thank you very much!