In SQL, RPAD()is used to pad the right part of a string with a specified character. The function can be used on strings and numbers, although depending on the DBMS, numbers may have to be passed as a string before they can be padded.
DBMSs that have an RPAD() function include MySQL, MariaDB, PostgreSQL, and Oracle.
DBMSs that don’t have an RPAD() function include SQL Server and SQLite.
Many RDBMSs have an INSTR() function that enables us to find a substring within a string. Some (such as MySQL and MariaDB) also have a LOCATE() function and a POSITION() function (also supported by PostgreSQL), that do a similar thing.
SQL Server doesn’t have an INSTR() function. Nor does it have a LOCATE() or POSITION() function. But it does have the CHARINDEX() function that does the same thing.
SQL Server also has the PATINDEX() function, which does a similar job to CHARINDEX().
PostgreSQL has a POSITION() function that returns the first starting index of a specified substring within a string.
If the substring doesn’t exist in the string, then zero is returned.
Continue readingIn PostgreSQL, RPAD() is a function that enables us to add padding to the right part of a string.
In PostgreSQL, LPAD()is a function that enables us to add padding to the left part of a string.
In PostgreSQL, the CONCAT_WS() function concatenates two or more strings, placing a separator between each one. The separator is specified by the first argument.
In PostgreSQL, the CONCAT() function concatenates the text representations of its arguments.
MariaDB has an INSTR() function and also a LOCATE() function. Both functions appear to do exactly the same thing – return the position of a substring within a string.
However, there is a difference.
Continue readingIf you need to replace a substring with another string in MariaDB, here are two approaches that you can use.
Continue readingMariaDB has an RTRIM() function and a RTRIM_ORACLE() function. Both functions do essentially the same thing. But there is a minor difference.