Comments
3 comments
-
Hi @adam_hafner
Thank you for reaching out on the Redgate forum regarding your SQL Scripts Manager behavioural concern.
I've replicated this on my test system, there is a parsing error when there is an ampersand character (&) in the CDATA section. I am of the belief that CDATA should be able to parse that character within an XML format.
Along with your other feature requests, I'll escalate this to our development team to see if this is determined to be a bug.
In the interim, I'd recommend using text replacements for this character to generate valid scripts for the application to parse.
-
@Jon_Kirkwood thanks for passing this along. I will wait to hear what you find out from your team.
-
Hi Adam,
Confirming that this is in our developer's backlog for implementation. There is not yet a confirmed release timeframe for the feature but is being investigated along with other features for their implementation.
Will update this forum post should the situation change and/or a release is available that includes this feature request.
Add comment
Please sign in to leave a comment.
```
```
Here is the error that is displayed:
I noticed that even when using the Script Generator via the UI, that if I put an ampersand in the `Description` it doesn't automatically convert the `&` to `&` either. That should also be addressed.