@Rajeev-Gupta ,
Hope now its very clear to you
You apparently didn’t read in my boilerplate where I explained how to mark the data as code using the </> button that’s on the toolbar when you are writing your post. It makes it much easier to know for sure what your data is without the forum mangling characters, and to distinguish your narrative from your data. Please use that.
Further, though you used more words to explain, what you didn’t do is say whether one or both of our solutions works for you.
Also, that semicolon is new information, which changes the regex. If you want helpful answers, you need to give us representative examples of your data, or you are going to have to be willing to edit the regex to meet your needs. And if you ask more questions, you will have to tell us what didn’t work for you (ie, did it not match anything? or did it match something, but not give the exact replacement you expected? or …)
Please help us help you by formatting the text as has been requested, and giving us example before and after data, without changing the expectations every post.
If I modify @Ekopalypse’s expression to include the semicolon and to use your more-specific replacement example:
find = (?-s)(set @queryName = '.+';\h*\R) – I added (?-s) to enforce .-does-not-match-newline, and added the semicolon that you didn’t tell us about.
replace = $1if @DebugMode > 1\r\nBEGIN\r\n********\r\nEND\r\n – I changed the IF statement, and included BEGIN/END wrappers
It turned the document:
set @queryName = 'InsertCNameforLessThan15';
blah
blah
set @queryName = 'InsertCNameforLessThan20';
halb
halb
into
set @queryName = 'InsertCNameforLessThan15';
if @DebugMode > 1
BEGIN
********
END
blah
blah
set @queryName = 'InsertCNameforLessThan20';
if @DebugMode > 1
BEGIN
********
END
halb
halb
Please notice how using the </> button has put the text into a plaintext box, and the ASCII quotes '...' do not get turned into smartquotes ‘...’, so it’s a more-accurate representation of your data.
Using Eko’s as the base, I was able to generate something that I think meets your expectations, assuming that **** isn’t supposed to include anything from the original match.
Using mine as the base,
find = (?-s)set @queryName = '(.*)';\h*(?:(\R)|\z)\K
replace = (?2:\r\n)if @DebugMode > 1\r\nBEGIN\r\n***** this allows your replacement to embed the matching string from the match = '$1' *****\r\nEND\r\n
(if we haven’t made it clear in our answers, all of these answers assume ☑ regular expression is enabled)
For my regex, modified for semicolon ; and your more-specific replacement, the *** will be able to include the text from inside your queryName string, so
set @queryName = 'InsertCNameforLessThan15';
blah
blah
set @queryName = 'InsertCNameforLessThan20';
which has the last line end with no newline character, will become
set @queryName = 'InsertCNameforLessThan15';
if @DebugMode > 1
BEGIN
***** this allows your replacement to embed the matching string from the match = 'InsertCNameforLessThan15' *****
END
blah
blah
set @queryName = 'InsertCNameforLessThan20';
if @DebugMode > 1
BEGIN
***** this allows your replacement to embed the matching string from the match = 'InsertCNameforLessThan20' *****
END
Both of these meet your expressed needs, and you should have been able to figure out how to put the semicolon after the closing ' to make it match for you.
At this point, I am done with freebies for you. If you show more effort – properly formatting your post so the data comes through, giving us representative data, telling us whether or not ours work, and what isn’t right (for example, saying “when I tried it with data xyz, your expression made it pdq, but I wanted pdqu; I tried modifying the regex to rr;r, because I thought adding the semicolon would make it match more accurately, but that made it say pdqv, which still isn’t quite what I wanted”) – if you show that level of effort, so that we can tell you’re trying to learn from us rather than mooch off us, then I’ll be willing to answer more well-formed questions about this regex. If you don’t, well, we’ve given enough that assuming your data was correct, it will work for you.
