RPAD¶

Syntax¶

RPAD( <base>, <length_expr> [, <pad>] )

Arguments¶

base

A VARCHAR or BINARY value.

length_expr

An expression that evaluates to an integer. It specifies:

• The number of UTF-8 characters to return if the input is VARCHAR.

• The number of bytes to return if the input is BINARY.

pad

A VARCHAR or BINARY value. The type must match the data type of the base argument. Characters (or bytes) from this argument are used to pad the base.

Returns¶

The data type of the returned value is the same as the data type of the base input value (VARCHAR or BINARY).

Usage notes¶

• If the base argument is longer than length_expr, it is truncated to length length_expr.

• The pad argument can be multiple characters/bytes long. The pad argument is repeated in the result until the desired length (length_expr) is reached, truncating any superfluous characters/bytes in the pad argument. If the pad argument is empty, no padding is inserted, but the result is still truncated to length length_expr.

• When base is a string, the default pad string is ' ' (a single blank space). When base is a binary value, the pad argument must be provided explicitly.

Collation details¶

• Collation applies to VARCHAR inputs. Collation doesn’t apply if the input data type of the first argument is BINARY.

• No impact. Although collation is accepted syntactically, collations have no impact on processing. For example, languages with two-character and three-character letters (for example, “dzs” in Hungarian, “ch” in Czech) still count those as two or three characters (not one character) for the length argument.

• The collation of the result is the same as the collation of the input. This can be useful if the returned value is passed to another function as part of nested function calls.

• Currently, Snowflake allows the base and pad arguments to have different collation specifiers. However, the individual collation specifiers can’t both be retained because the returned value has only one collation specifier. Snowflake recommends that you avoid using pad strings that have a different collation from the base string.

Examples¶

These examples use the RPAD function to pad VARCHAR and BINARY data on the right.

Create and fill a table:

CREATE OR REPLACE TABLE padding_example (v VARCHAR, b BINARY);

INSERT INTO padding_example (v, b)
  SELECT
    'Hi',
    HEX_ENCODE('Hi');

INSERT INTO padding_example (v, b)
  SELECT
    '-123.00',
    HEX_ENCODE('-123.00');

INSERT INTO padding_example (v, b)
  SELECT
    'Twelve Dollars',
    TO_BINARY(HEX_ENCODE('Twelve Dollars'), 'HEX');

Query the table to show the data:

SELECT * FROM padding_example;

+----------------+------------------------------+
| V              | B                            |
|----------------+------------------------------|
| Hi             | 4869                         |
| -123.00        | 2D3132332E3030               |
| Twelve Dollars | 5477656C766520446F6C6C617273 |
+----------------+------------------------------+

This example demonstrates right-padding of VARCHAR values using the RPAD function, with the results limited to 10 characters:

SELECT v,
       RPAD(v, 10, '_') AS pad_with_underscore,
       RPAD(v, 10, '$') AS pad_with_dollar_sign
  FROM padding_example
  ORDER BY v;

+----------------+---------------------+----------------------+
| V              | PAD_WITH_UNDERSCORE | PAD_WITH_DOLLAR_SIGN |
|----------------+---------------------+----------------------|
| -123.00        | -123.00___          | -123.00$$$           |
| Hi             | Hi________          | Hi$$$$$$$$           |
| Twelve Dollars | Twelve Dol          | Twelve Dol           |
+----------------+---------------------+----------------------+

This example demonstrates right-padding of BINARY values using the RPAD function, with the results limited to 10 bytes:

SELECT b,
       RPAD(b, 10, TO_BINARY(HEX_ENCODE('_'))) AS pad_with_underscore,
       RPAD(b, 10, TO_BINARY(HEX_ENCODE('$'))) AS pad_with_dollar_sign
  FROM padding_example
  ORDER BY b;

+------------------------------+----------------------+----------------------+
| B                            | PAD_WITH_UNDERSCORE  | PAD_WITH_DOLLAR_SIGN |
|------------------------------+----------------------+----------------------|
| 2D3132332E3030               | 2D3132332E30305F5F5F | 2D3132332E3030242424 |
| 4869                         | 48695F5F5F5F5F5F5F5F | 48692424242424242424 |
| 5477656C766520446F6C6C617273 | 5477656C766520446F6C | 5477656C766520446F6C |
+------------------------------+----------------------+----------------------+

This example shows right-padding when multiple characters are used and when the padding isn’t an even multiple of the length of the multi-character string used for padding:

SELECT RPAD('123.50', 19, '*_');

+--------------------------+
| RPAD('123.50', 19, '*_') |
|--------------------------|
| 123.50*_*_*_*_*_*_*      |
+--------------------------+

The output shows that 19 characters were returned, and the last * character doesn’t have an accompanying _ character.