New functions STR_SUBSTRING_AFTER and STR_SUBSTRING_BEFORE

[oswaldobapvicjr]

This push introduces new string functions:

• STR_SUBSTRING_AFTER(string, separator)
• STR_SUBSTRING_BEFORE(string, separator)

Examples:

• STR_SUBSTRING_AFTER("file.json", ".")
  • returns "json"
• STR_SUBSTRING_BEFORE("2024/10/23", "/")
  • returns "2024"

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[uklimaschewski]

Why not defining a single method STR_SPLIT(string, separator)? It could return an array of strings (similar to String.split(String regex)).

Using STR_SPLIT("file.json", ".")[1] would return "json".
Using STR_SPLIT("2024/10/23", "/")[0] would return "2024".

You would even have much more possibilities.

I am just unsure of using a regex or just a simple string as separator is better.

[oswaldobapvicjr]

@uklimaschewski, the functions STR_SUBSTRING_AFTER and STR_SUBSTRING_BEFORE were inspired by those provided by leading tools such as XPath (W3C), Microsoft Excel, and MuleSoft by Salesforce so I wonder it could be good here too, for simplicity and assimilation. However, I agree that the same result could be obtained using STR_SPLIT.

Regarding the doubt whether to use a regex or a separator, why not implement both? ;)

• STR_SPLIT("file.json", ".") would return "json" (simple and direct for everyone)
• STR_SPLIT_REGEX("file.json", "\\.") would also return "json", but since it's regex-based, it offers more possibilities for users that are familiar with regex.