Scalar functions

Scalar functions are functions that return scalars.

String functions

concat('first_arg', second_arg, [ parameter , ... ])

Concatenates a variable number of arguments into a single string. It ignores NULL values.

Returns: text

1. cr> select concat('foo', null, 'bar') AS col;
2. +--------+
3. | col    |
4. +--------+
5. | foobar |
6. +--------+
7. SELECT 1 row in set (... sec)

You can also use the || operator:

1. cr> select 'foo' || 'bar' AS col;
2. +--------+
3. | col    |
4. +--------+
5. | foobar |
6. +--------+
7. SELECT 1 row in set (... sec)

format('format_string', parameter, [ parameter , ... ])

Formats a string similar to the C function printf. For details about the format string syntax, see formatter

Returns: text

1. cr> select format('%s.%s', schema_name, table_name)  AS fqtable
2. ... from sys.shards
3. ... where table_name = 'locations'
4. ... limit 1;
5. +---------------+
6. | fqtable       |
7. +---------------+
8. | doc.locations |
9. +---------------+
10. SELECT 1 row in set (... sec)

1. cr> select format('%tY', date) AS year
2. ... from locations
3. ... group by format('%tY', date)
4. ... order by 1;
5. +------+
6. | year |
7. +------+
8. | 1979 |
9. | 2013 |
10. +------+
11. SELECT 2 rows in set (... sec)

substr('string', from, [ count ])

Extracts a part of a string. from specifies where to start and count the length of the part.

Returns: text

1. cr> select substr('crate.io', 3, 2) AS substr;
2. +--------+
3. | substr |
4. +--------+
5. | at     |
6. +--------+
7. SELECT 1 row in set (... sec)

char_length('string')

Counts the number of characters in a string.

Returns: integer

1. cr> select char_length('crate.io') AS char_length;
2. +-------------+
3. | char_length |
4. +-------------+
5. |           8 |
6. +-------------+
7. SELECT 1 row in set (... sec)

Each character counts only once, regardless of its byte size.

1. cr> select char_length('©rate.io') AS char_length;
2. +-------------+
3. | char_length |
4. +-------------+
5. |           8 |
6. +-------------+
7. SELECT 1 row in set (... sec)

length(text)

Returns the number of characters in a string.

The same as char_length.

bit_length('string')

Counts the number of bits in a string.

Returns: integer

Note

CrateDB uses UTF-8 encoding internally, which uses between 1 and 4 bytes per character.

1. cr> select bit_length('crate.io') AS bit_length;
2. +------------+
3. | bit_length |
4. +------------+
5. |         64 |
6. +------------+
7. SELECT 1 row in set (... sec)

1. cr> select bit_length('©rate.io') AS bit_length;
2. +------------+
3. | bit_length |
4. +------------+
5. |         72 |
6. +------------+
7. SELECT 1 row in set (... sec)

octet_length('string')

Counts the number of bytes (octets) in a string.

Returns: integer

1. cr> select octet_length('crate.io') AS octet_length;
2. +--------------+
3. | octet_length |
4. +--------------+
5. |            8 |
6. +--------------+
7. SELECT 1 row in set (... sec)

1. cr> select octet_length('©rate.io') AS octet_length;
2. +--------------+
3. | octet_length |
4. +--------------+
5. |            9 |
6. +--------------+
7. SELECT 1 row in set (... sec)

ascii(string)

Returns the ASCII code of the first character. For UTF-8, returns the Unicode code point of the characters.

Returns: int

1. cr> SELECT ascii('a') AS a, ascii('🎈') AS b;
2. +----+--------+
3. |  a |      b |
4. +----+--------+
5. | 97 | 127880 |
6. +----+--------+
7. SELECT 1 row in set (... sec)

chr(int)

Returns the character with the given code. For UTF-8 the argument is treated as a Unicode code point.

Returns: string

1. cr> SELECT chr(65) AS a;
2. +---+
3. | a |
4. +---+
5. | A |
6. +---+
7. SELECT 1 row in set (... sec)

lower('string')

Converts all characters to lowercase. lower does not perform locale-sensitive or context-sensitive mappings.

Returns: text

1. cr> select lower('TransformMe') AS lower;
2. +-------------+
3. | lower       |
4. +-------------+
5. | transformme |
6. +-------------+
7. SELECT 1 row in set (... sec)

upper('string')

Converts all characters to uppercase. upper does not perform locale-sensitive or context-sensitive mappings.

Returns: text

1. cr> select upper('TransformMe') as upper;
2. +-------------+
3. | upper       |
4. +-------------+
5. | TRANSFORMME |
6. +-------------+
7. SELECT 1 row in set (... sec)

initcap('string')

Converts the first letter of each word to upper case and the rest to lower case (capitalize letters).

Returns: text

1. cr> select initcap('heLlo WORLD') AS initcap;
2. +-------------+
3. | initcap     |
4. +-------------+
5. | Hello World |
6. +-------------+
7. SELECT 1 row in set (... sec)

sha1('string')

Returns: text

Computes the SHA1 checksum of the given string.

1. cr> select sha1('foo') AS sha1;
2. +------------------------------------------+
3. | sha1                                     |
4. +------------------------------------------+
5. | 0beec7b5ea3f0fdbc95d0dd47f3c5bc275da8a33 |
6. +------------------------------------------+
7. SELECT 1 row in set (... sec)

md5('string')

Returns: text

Computes the MD5 checksum of the given string.

See sha1 for an example.

replace(text, from, to)

Replaces all occurrences of from in text with to.

1. cr> select replace('Hello World', 'World', 'Stranger') AS hello;
2. +----------------+
3. | hello          |
4. +----------------+
5. | Hello Stranger |
6. +----------------+
7. SELECT 1 row in set (... sec)

translate(string, from, to)

Performs several single-character, one-to-one translation in one operation. It translates string by replacing the characters in the from set, one-to-one positionally, with their counterparts in the to set. If from is longer than to, the function removes the occurrences of the extra characters in from. If there are repeated characters in from, only the first mapping is considered.

Synopsis:

1. translate(string, from, to)

Examples:

1. cr> select translate('Crate', 'Ct', 'Dk') as translation;
2. +-------------+
3. | translation |
4. +-------------+
5. | Drake       |
6. +-------------+
7. SELECT 1 row in set (... sec)

1. cr> select translate('Crate', 'rCe', 'c') as translation;
2. +-------------+
3. | translation |
4. +-------------+
5. | cat         |
6. +-------------+
7. SELECT 1 row in set (... sec)

trim({LEADING | TRAILING | BOTH} 'str_arg_1' FROM 'str_arg_2')

Removes the longest string containing characters from str_arg_1 (' ' by default) from the start, end, or both ends (BOTH is the default) of str_arg_2.

Synopsis:

1. trim([ [ {LEADING | TRAILING | BOTH} ] [ str_arg_1 ] FROM ] str_arg_2)

Examples

1. cr> select trim(BOTH 'ab' from 'abcba') AS trim;
2. +------+
3. | trim |
4. +------+
5. | c    |
6. +------+
7. SELECT 1 row in set (... sec)

1. cr> select trim('ab' from 'abcba') AS trim;
2. +------+
3. | trim |
4. +------+
5. | c    |
6. +------+
7. SELECT 1 row in set (... sec)

1. cr> select trim('   abcba   ') AS trim;
2. +-------+
3. | trim  |
4. +-------+
5. | abcba |
6. +-------+
7. SELECT 1 row in set (... sec)

ltrim(text, [ trimmingText ])

Removes set of characters which are matching trimmingText (' ' by default) to the left of text.

1. cr> select ltrim('xxxzzzabcba', 'xz') AS ltrim;
2. +-------+
3. | ltrim |
4. +-------+
5. | abcba |
6. +-------+
7. SELECT 1 row in set (... sec)

rtrim(text, [ trimmingText ])

Removes set of characters which are matching trimmingText (' ' by default) to the right of text.

1. cr> select rtrim('abcbaxxxzzz', 'xz') AS rtrim;
2. +-------+
3. | rtrim |
4. +-------+
5. | abcba |
6. +-------+
7. SELECT 1 row in set (... sec)

quote_ident(text)

Returns: text

Quotes a provided string argument. Quotes are added only if necessary. For example, if the string contains non-identifier characters, keywords or would be case-folded. Embedded quotes are properly doubled.

The quoted string can be used as an identifier in an SQL statement.

1. cr> select quote_ident('Column name') AS quoted;
2. +---------------+
3. | quoted        |
4. +---------------+
5. | "Column name" |
6. +---------------+
7. SELECT 1 row in set (... sec)

left('string', len)

Returns the first len characters of string when len > 0, otherwise all but last len characters.

Synopsis:

1. left(string, len)

Examples:

1. cr> select left('crate.io', 5) AS col;
2. +-------+
3. | col   |
4. +-------+
5. | crate |
6. +-------+
7. SELECT 1 row in set (... sec)

1. cr> select left('crate.io', -3) AS col;
2. +-------+
3. | col   |
4. +-------+
5. | crate |
6. +-------+
7. SELECT 1 row in set (... sec)

right('string', len)

Returns the last len characters in string when len > 0, otherwise all but first len characters.

Synopsis:

1. right(string, len)

Examples:

1. cr> select right('crate.io', 2) AS col;
2. +-----+
3. | col |
4. +-----+
5. | io  |
6. +-----+
7. SELECT 1 row in set (... sec)

1. cr> select right('crate.io', -6) AS col;
2. +-----+
3. | col |
4. +-----+
5. | io  |
6. +-----+
7. SELECT 1 row in set (... sec)

lpad('string1', len[, 'string2'])

Fill up string1 to length len by prepending the characters string2 (a space by default). If string1 is already longer than len then it is truncated (on the right).

Synopsis:

1. lpad(string1, len[, string2])

Example:

1. cr> select lpad(' I like CrateDB!!', 41, 'yes! ') AS col;
2. +-------------------------------------------+
3. | col                                       |
4. +-------------------------------------------+
5. | yes! yes! yes! yes! yes! I like CrateDB!! |
6. +-------------------------------------------+
7. SELECT 1 row in set (... sec)

rpad('string1', len[, 'string2'])

Fill up string1 to length len by appending the characters string2 (a space by default). If string1 is already longer than len then it is truncated.

Synopsis:

1. rpad(string1, len[, string2])

Example:

1. cr> select rpad('Do you like Crate?', 38, ' yes!') AS col;
2. +----------------------------------------+
3. | col                                    |
4. +----------------------------------------+
5. | Do you like Crate? yes! yes! yes! yes! |
6. +----------------------------------------+
7. SELECT 1 row in set (... sec)

Note

In both cases, the scalar functions lpad and rpad, do now accept a len greater than 50000.

encode(bytea, format)

Encode takes a binary string (hex format) and returns a text encoding using the specified format. Supported formats are: base64, hex, and escape. The escape format replaces unprintable characters with octal byte notation like \nnn. For the reverse function, see decode().

Synopsis:

1. encode(string1, format)

Example:

1. cr> select encode(E'123\b\t56', 'base64') AS col;
2. +--------------+
3. | col          |
4. +--------------+
5. | MTIzCAk1Ng== |
6. +--------------+
7. SELECT 1 row in set (... sec)

decode(text, format)

Decodes a text encoded string using the specified format and returns a binary string (hex format). Supported formats are: base64, hex, and escape. For the reverse function, see encode().

Synopsis:

1. decode(text1, format)

Example:

1. cr> select decode('T\214', 'escape') AS col;
2. +--------+
3. | col    |
4. +--------+
5. | \x548c |
6. +--------+
7. SELECT 1 row in set (... sec)

repeat(text, integer)

Repeats a string the specified number of times.

If the number of repetitions is equal or less than zero then the function returns an empty string.

Returns: text

1. cr> select repeat('ab', 3) AS repeat;
2. +--------+
3. | repeat |
4. +--------+
5. | ababab |
6. +--------+
7. SELECT 1 row in set (... sec)

split_part(text, text, integer)

Splits a string into parts using a delimiter and returns the part at the given index. The first part is addressed by index 1.

Special Cases:

• Returns the empty string if the index is greater than the number of parts.
• If any of the arguments is NULL, the result is NULL.
• If the delimiter is the empty string, the input string is considered as consisting of exactly one part.

Returns: text

Synopsis:

1. split_part(string, delimiter, index)

Example:

1. cr> select split_part('ab--cdef--gh', '--', 2) AS part;
2. +------+
3. | part |
4. +------+
5. | cdef |
6. +------+
7. SELECT 1 row in set (... sec)

Date and time functions

date_trunc('interval', ['timezone',] timestamp)

Returns: timestamp with time zone

Limits a timestamps precision to a given interval.

Valid intervals are:

• second
• minute
• hour
• day
• week
• month
• quarter
• year

Valid values for timezone are either the name of a time zone (for example ‘Europe/Vienna’) or the UTC offset of a time zone (for example ‘+01:00’). To get a complete overview of all possible values take a look at the available time zones supported by Joda-Time.

The following example shows how to use the date_trunc function to generate a day based histogram in the Europe/Moscow timezone:

1. cr> select
2. ... date_trunc('day', 'Europe/Moscow', date) as day,
3. ... count(*) as num_locations
4. ... from locations
5. ... group by 1
6. ... order by 1;
7. +---------------+---------------+
8. | day           | num_locations |
9. +---------------+---------------+
10. | 308523600000  | 4             |
11. | 1367352000000 | 1             |
12. | 1373918400000 | 8             |
13. +---------------+---------------+
14. SELECT 3 rows in set (... sec)

If you don’t specify a time zone, truncate uses UTC time:

1. cr> select date_trunc('day', date) as day, count(*) as num_locations
2. ... from locations
3. ... group by 1
4. ... order by 1;
5. +---------------+---------------+
6. | day           | num_locations |
7. +---------------+---------------+
8. | 308534400000  | 4             |
9. | 1367366400000 | 1             |
10. | 1373932800000 | 8             |
11. +---------------+---------------+
12. SELECT 3 rows in set (... sec)

extract(field from source)

extract is a special expression that translates to a function which retrieves subfields such as day, hour or minute from a timestamp.

The return type depends on the used field.

Synopsis

1. EXTRACT( field FROM expression )

field

An identifier or string literal which identifies the part of the timestamp that should be extracted.

expression

An expression that resolves to a timestamp data type with or without timezone or is castable to timestamp data types.

1. cr> select extract(day from '2014-08-23') AS day;
2. +-----+
3. | day |
4. +-----+
5. |  23 |
6. +-----+
7. SELECT 1 row in set (... sec)

source must be an expression that returns a timestamp. In case the expression has a different return type but is known to be castable to timestamp an implicit cast will be attempted.

field is an identifier that selects which part of the timestamp to extract. The following fields are supported:

CENTURY

Return type: integer

century of era

Returns the ISO representation which is a straight split of the date.

Year 2000 century 20 and year 2001 is also century 20. This is different to the GregorianJulian (GJ) calendar system where 2001 would be century 21.

YEAR

Return type: integer

the year field

QUARTER

Return type: integer

the quarter of the year (1 - 4)

MONTH

Return type: integer

the month of the year

WEEK

Return type: integer

the week of the year

DAY

Return type: integer

the day of the month

DAY_OF_MONTH

Return type: integer

same as day

DAY_OF_WEEK

Return type: integer

day of the week. Starting with Monday (1) to Sunday (7)

DOW

Return type: integer

same as day_of_week

DAY_OF_YEAR

Return type: integer

the day of the year (1 - 365 / 366)

DOY

Return type: integer

same as day_of_year

HOUR

Return type: integer

the hour field

MINUTE

Return type: integer

the minute field

SECOND

Return type: integer

the second field

EPOCH

Return type: double precision

The number of seconds since Jan 1, 1970.

Can be negative if earlier than Jan 1, 1970.

CURRENT_TIME

The CURRENT_TIME expression returns the time in microseconds since midnight UTC at the time the SQL statement was handled. Clock time is looked up at most once within the scope of a single query, to ensure that multiple occurrences of CURRENT_TIME evaluate to the same value.

synopsis:

1. CURRENT_TIME [ ( precision ) ]

precision must be a positive integer between 0 and 6. The default value is 6. It determines the number of fractional seconds to output. A value of 0 means the time will have second precision, no fractional seconds (microseconds) are given.

Note

No guarantee is provided about the accuracy of the underlying clock, results may be limited to millisecond precision, depending on the system.

CURRENT_TIMESTAMP

The CURRENT_TIMESTAMP expression returns the timestamp in milliseconds since epoch at the time the SQL statement was handled. Therefore, the same timestamp value is returned for every invocation of a single statement.

Synopsis:

1. CURRENT_TIMESTAMP [ ( precision ) ]

Here, precision must be a positive integer between 0 and 3. The default value is 3. This value determines the number of fractional seconds to output. A value of 0 means the timestamp will have second precision, no fractional seconds (milliseconds) are given.

Tip

To get an offset value of CURRENT_TIMESTAMP (e.g., this same time one day ago), you can add or subtract an interval, like so:

1. CURRENT_TIMESTAMP - '1 day'::interval

Note

If the CURRENT_TIMESTAMP function is used in Generated columns it behaves slightly different in UPDATE operations. In such a case the actual timestamp of each row update is returned.

The return value of expressions CURRENT_TIMESTAMP and CURRENT_TIME depends on the system clock and the JVM implementation.

CURDATE()

The CURDATE() scalar function is an alias of the CURRENT_DATE expression. See CURRENT_DATE.

synopsis:

1. CURDATE()

CURRENT_DATE

The CURRENT_DATE expression returns the date in UTC timezone at the time the SQL statement was handled. Clock time is looked up at most once within the scope of a single query, to ensure that multiple occurrences of CURRENT_DATE evaluate to the same value.

synopsis:

1. CURRENT_DATE

now()

Returns the current date and time.

This is the same as current_timestamp

Returns: timestamp with time zone

Synopsis:

1. now()

date_format([format_string, [timezone,]] timestamp)

The date_format function formats a timestamp as string according to the (optional) format string.

Returns: text

Synopsis

1. DATE_FORMAT( [ format_string, [ timezone, ] ] timestamp )

The only mandatory argument is the timestamp value to format. It can be any expression that is safely convertible to timestamp data type with or without timezone.

Format

The syntax for the format_string is 100% compatible to the syntax of the MySQL date_format function. For reference, the format is listed in detail below 1:

date_format Format

If no format_string is given the default format will be used:

1. %Y-%m-%dT%H:%i:%s.%fZ

1. cr> select date_format('1970-01-01') as epoque;
2. +-----------------------------+
3. | epoque                      |
4. +-----------------------------+
5. | 1970-01-01T00:00:00.000000Z |
6. +-----------------------------+
7. SELECT 1 row in set (... sec)

Timezone

Valid values for timezone are either the name of a time zone (for example ‘Europe/Vienna’) or the UTC offset of a time zone (for example ‘+01:00’). To get a complete overview of all possible values take a look at the available time zones supported by Joda-Time.

The timezone will be UTC if not provided:

1. cr> select date_format('%W the %D of %M %Y %H:%i %p', 0) as epoque;
2. +-------------------------------------------+
3. | epoque                                    |
4. +-------------------------------------------+
5. | Thursday the 1st of January 1970 00:00 AM |
6. +-------------------------------------------+
7. SELECT 1 row in set (... sec)

1. cr> select date_format('%Y/%m/%d %H:%i', 'EST',  0) as est_epoque;
2. +------------------+
3. | est_epoque       |
4. +------------------+
5. | 1969/12/31 19:00 |
6. +------------------+
7. SELECT 1 row in set (... sec)

timezone(timezone, timestamp)

The timezone scalar function converts values of timestamp without time zone to/from timestamp with time zone.

Synopsis

1. TIMEZONE(timezone, timestamp)

It has two variants depending on the type of timestamp:

1. cr> select
2. ... 257504400000 as no_tz,
3. ... date_format('%Y-%m-%d %h:%i', 257504400000) as no_tz_str,
4. ... timezone('Europe/Madrid', 257504400000) as in_madrid,
5. ... date_format('%Y-%m-%d %h:%i', timezone('Europe/Madrid',
6. ... 257504400000)) as in_madrid_str;
7. +--------------+------------------+--------------+------------------+
8. |        no_tz | no_tz_str        |    in_madrid | in_madrid_str    |
9. +--------------+------------------+--------------+------------------+
10. | 257504400000 | 1978-02-28 09:00 | 257500800000 | 1978-02-28 08:00 |
11. +--------------+------------------+--------------+------------------+
12. SELECT 1 row in set (... sec)

1. cr> select
2. ... timezone('Europe/Madrid',
3. ... '1978-02-28T10:00:00.000+01:00'::timestamp with time zone) as epoque,
4. ... date_format('%Y-%m-%d %h:%i', timezone('Europe/Madrid',
5. ... '1978-02-28T10:00:00.000+01:00'::timestamp with time zone)) as epoque_str;
6. +--------------+------------------+
7. |       epoque | epoque_str       |
8. +--------------+------------------+
9. | 257508000000 | 1978-02-28 10:00 |
10. +--------------+------------------+
11. SELECT 1 row in set (... sec)

1. cr> select
2. ... timezone('Europe/Madrid',
3. ... '1978-02-28T10:00:00.000+01:00'::timestamp without time zone) as epoque,
4. ... date_format('%Y-%m-%d %h:%i', timezone('Europe/Madrid',
5. ... '1978-02-28T10:00:00.000+01:00'::timestamp without time zone)) as epoque_str;
6. +--------------+------------------+
7. |       epoque | epoque_str       |
8. +--------------+------------------+
9. | 257504400000 | 1978-02-28 09:00 |
10. +--------------+------------------+
11. SELECT 1 row in set (... sec)

to_char(expression, format_string)

The to_char function converts a timestamp or interval value to a string, based on a given format string.

Returns: text

Synopsis

1. TO_CHAR( expression, format_string )

expression can be any value with the type of timestamp (with or without a timezone) or interval.

Format

The syntax for the format_string differs based the type of the expression. For timestamp expressions, the format_string is a template string containing any of the following symbols:

1. cr> select to_char(timestamp '1970-01-01T17:31:12', 'Day, Month DD - HH12:MI AM YYYY AD') as ts;
2. +-----------------------------------------+
3. | ts                                      |
4. +-----------------------------------------+
5. | Thursday, January 01 - 05:31 PM 1970 AD |
6. +-----------------------------------------+
7. SELECT 1 row in set (... sec)

For interval expressions, the formatting string accepts the same tokens as timestamp expressions. The function then uses the timestamp of the specified interval added to the timestamp of 0000/01/01 00:00:00:

1. cr> select to_char(interval '1 year 3 weeks 200 minutes', 'YYYY MM DD HH12:MI:SS') as interval;
2. +---------------------+
3. | interval            |
4. +---------------------+
5. | 0001 01 22 03:20:00 |
6. +---------------------+
7. SELECT 1 row in set (... sec)

Geo functions

distance(geo_point1, geo_point2)

Returns: double precision

The distance function can be used to calculate the distance between two points on earth. It uses the Haversine formula which gives great-circle distances between 2 points on a sphere based on their latitude and longitude.

The return value is the distance in meters.

Below is an example of the distance function where both points are specified using WKT. See geo_point for more information on the implicit type casting of geo points:

1. cr> select distance('POINT (10 20)', 'POINT (11 21)') AS col;
2. +-------------------+
3. |               col |
4. +-------------------+
5. | 152354.3209044634 |
6. +-------------------+
7. SELECT 1 row in set (... sec)

This scalar function can always be used in both the WHERE and ORDER BY clauses. With the limitation that one of the arguments must be a literal and the other argument must be a column reference.

Note

The algorithm of the calculation which is used when the distance function is used as part of the result column list has a different precision than what is stored inside the index which is utilized if the distance function is part of a WHERE clause.

For example if select distance(...) returns 0.0 an equality check with where distance(...) = 0 might not yield anything at all due to the precision difference.

within(shape1, shape2)

Returns: boolean

The within function returns true if shape1 is within shape2. If that is not the case false is returned.

shape1 can either be a geo_shape or a geo_point. shape2 must be a geo_shape.

Below is an example of the within function which makes use of the implicit type casting from strings in WKT representation to geo point and geo shapes:

1. cr> select within(
2. ...   'POINT (10 10)',
3. ...   'POLYGON ((5 5, 10 5, 10 10, 5 10, 5 5))'
4. ... ) AS is_within;
5. +-----------+
6. | is_within |
7. +-----------+
8. | TRUE      |
9. +-----------+
10. SELECT 1 row in set (... sec)

This function can always be used within the WHERE clause.

intersects(geo_shape, geo_shape)

Returns: boolean

The intersects function returns true if both argument shapes share some points or area, they overlap. This also includes two shapes where one lies within the other.

If false is returned, both shapes are considered disjoint.

Example:

1. cr> select
2. ... intersects(
3. ...   {type='Polygon', coordinates=[
4. ...         [[13.4252, 52.7096],[13.9416, 52.0997],
5. ...          [12.7221, 52.1334],[13.4252, 52.7096]]]},
6. ...   'LINESTRING(13.9636 52.6763, 13.2275 51.9578,
7. ...               12.9199 52.5830, 11.9970 52.6830)'
8. ... ) as intersects,
9. ... intersects(
10. ...   {type='Polygon', coordinates=[
11. ...         [[13.4252, 52.7096],[13.9416, 52.0997],
12. ...          [12.7221, 52.1334],[13.4252, 52.7096]]]},
13. ...   'LINESTRING (11.0742 49.4538, 11.5686 48.1367)'
14. ... ) as disjoint;
15. +------------+----------+
16. | intersects | disjoint |
17. +------------+----------+
18. | TRUE       | FALSE    |
19. +------------+----------+
20. SELECT 1 row in set (... sec)

Due to a limitation on the geo_shape datatype this function cannot be used in the ORDER BY clause.

latitude(geo_point) and longitude(geo_point)

Returns: double precision

The latitude and longitude function return the coordinates of latitude or longitude of a point, or NULL if not available. The input must be a column of type geo_point, a valid WKT string or a double precision array. See geo_point for more information on the implicit type casting of geo points.

Example:

1. cr> select mountain, height, longitude(coordinates) as "lon", latitude(coordinates) as "lat"
2. ... from sys.summits order by height desc limit 1;
3. +------------+--------+---------+---------+
4. | mountain   | height |     lon |     lat |
5. +------------+--------+---------+---------+
6. | Mont Blanc |   4808 | 6.86444 | 45.8325 |
7. +------------+--------+---------+---------+
8. SELECT 1 row in set (... sec)

Below is an example of the latitude/longitude functions which make use of the implicit type casting from strings to geo point:

1. cr> select latitude('POINT (10 20)') AS lat, longitude([10.0, 20.0]) AS long;
2. +------+------+
3. |  lat | long |
4. +------+------+
5. | 20.0 | 10.0 |
6. +------+------+
7. SELECT 1 row in set (... sec)

geohash(geo_point)

Returns: text

Returns a GeoHash representation based on full precision (12 characters) of the input point, or NULL if not available. The input has to be a column of type geo_point, a valid WKT string or a double precision array. See geo_point for more information of the implicit type casting of geo points.

Example:

1. cr> select mountain, height, geohash(coordinates) as "geohash" from sys.summits
2. ... order by height desc limit 1;
3. +------------+--------+--------------+
4. | mountain   | height | geohash      |
5. +------------+--------+--------------+
6. | Mont Blanc |   4808 | u0huspw99j1r |
7. +------------+--------+--------------+
8. SELECT 1 row in set (... sec)

Mathematical functions

All mathematical functions can be used within WHERE and ORDER BY clauses.

abs(number)

Returns the absolute value of the given number in the datatype of the given number:

1. cr> select abs(214748.0998) AS a, abs(0) AS b, abs(-214748) AS c;
2. +-------------+---+--------+
3. |           a | b |      c |
4. +-------------+---+--------+
5. | 214748.0998 | 0 | 214748 |
6. +-------------+---+--------+
7. SELECT 1 row in set (... sec)

ceil(number)

Returns the smallest integer or long value that is not less than the argument.

Returns: bigint or integer

Return value will be of type integer if the input value is an integer or float. If the input value is of type bigint or double precision the return value will be of type bigint:

1. cr> select ceil(29.9) AS col;
2. +-----+
3. | col |
4. +-----+
5. |  30 |
6. +-----+
7. SELECT 1 row in set (... sec)

ceiling(number)

This is an alias for ceil.

degrees(double precision)

Convert the given radians value to degrees.

Returns: double precision

1. cr> select degrees(0.5) AS degrees;
2. +-------------------+
3. |           degrees |
4. +-------------------+
5. | 28.64788975654116 |
6. +-------------------+
7. SELECT 1 row in set (... sec)

exp(number)

Returns Euler’s number e raised to the power of the given numeric value. The output will be cast to the given input type and thus may loose precision.

Returns: Same as input type.

1. cr> select exp(1.0) AS exp;
2. +-------------------+
3. |               exp |
4. +-------------------+
5. | 2.718281828459045 |
6. +-------------------+
7. SELECT 1 row in set (... sec)

floor(number)

Returns the largest integer or long value that is not greater than the argument.

Returns: bigint or integer

Return value will be an integer if the input value is an integer or a float. If the input value is of type bigint or double precision the return value will be of type bigint.

See below for an example:

1. cr> select floor(29.9) AS floor;
2. +-------+
3. | floor |
4. +-------+
5. |    29 |
6. +-------+
7. SELECT 1 row in set (... sec)

ln(number)

Returns the natural logarithm of given number.

Returns: double precision

See below for an example:

1. cr> SELECT ln(1) AS ln;
2. +-----+
3. |  ln |
4. +-----+
5. | 0.0 |
6. +-----+
7. SELECT 1 row in set (... sec)

Note

An error is returned for arguments which lead to undefined or illegal results. E.g. ln(0) results in minus infinity, and therefore, an error is returned.

log(x : number, b : number)

Returns the logarithm of given x to base b.

Returns: double precision

See below for an example, which essentially is the same as above:

1. cr> SELECT log(100, 10) AS log;
2. +-----+
3. | log |
4. +-----+
5. | 2.0 |
6. +-----+
7. SELECT 1 row in set (... sec)

The second argument (b) is optional. If not present, base 10 is used:

1. cr> SELECT log(100) AS log;
2. +-----+
3. | log |
4. +-----+
5. | 2.0 |
6. +-----+
7. SELECT 1 row in set (... sec)

Note

An error is returned for arguments which lead to undefined or illegal results. E.g. log(0) results in minus infinity, and therefore, an error is returned.

The same is true for arguments which lead to a division by zero, as e.g. log(10, 1) does.

modulus(y, x)

Returns the remainder of y/x.

Returns: Same as argument types.

1. cr> select modulus(5, 4) AS mod;
2. +-----+
3. | mod |
4. +-----+
5. |   1 |
6. +-----+
7. SELECT 1 row in set (... sec)

mod(y, x)

This is an alias for modulus.

power(a: number, b: number)

Returns the given argument a raised to the power of argument b.

Returns: double precision

The return type of the power function is always double precision, even when both the inputs are integral types, in order to be consistent across positive and negative exponents (which will yield decimal types).

See below for an example:

1. cr> SELECT power(2,3) AS pow;
2. +-----+
3. | pow |
4. +-----+
5. | 8.0 |
6. +-----+
7. SELECT 1 row in set (... sec)

radians(double precision)

Convert the given degrees value to radians.

Returns: double precision

1. cr> select radians(45.0) AS radians;
2. +--------------------+
3. |            radians |
4. +--------------------+
5. | 0.7853981633974483 |
6. +--------------------+
7. SELECT 1 row in set (... sec)

random()

The random function returns a random value in the range 0.0 <= X < 1.0.

Returns: double precision

Note

Every call to random will yield a new random number.

gen_random_text_uuid()

Returns a random time based UUID as text. The returned ID is similar to flake IDs and well suited for use as primary key value.

Note that the ID is opaque (i.e., not to be considered meaningful in any way) and the implementation is free to change.

round(number)

If the input is of type double precision or bigint the result is the closest bigint to the argument, with ties rounding up.

If the input is of type real or integer the result is the closest integer to the argument, with ties rounding up.

Returns: bigint or integer

See below for an example:

1. cr> select round(42.2) AS round;
2. +-------+
3. | round |
4. +-------+
5. |    42 |
6. +-------+
7. SELECT 1 row in set (... sec)

trunc(number[, precision])

Returns number truncated to the specified precision (decimal places).

When precision is not specified, the result’s type is an integer, or bigint. When it is specified, the result’s type is double precision. Notice that trunc(number) and trunc(number, 0) return different result types.

See below for examples:

1. cr> select trunc(29.999999, 3) AS trunc;
2. +--------+
3. |  trunc |
4. +--------+
5. | 29.999 |
6. +--------+
7. SELECT 1 row in set (... sec)

9. cr> select trunc(29.999999) AS trunc;
10. +-------+
11. | trunc |
12. +-------+
13. |    29 |
14. +-------+
15. SELECT 1 row in set (... sec)

sqrt(number)

Returns the square root of the argument.

Returns: double precision

See below for an example:

1. cr> select sqrt(25.0) AS sqrt;
2. +------+
3. | sqrt |
4. +------+
5. |  5.0 |
6. +------+
7. SELECT 1 row in set (... sec)

sin(number)

Returns the sine of the argument.

Returns: double precision

See below for an example:

1. cr> SELECT sin(1) AS sin;
2. +--------------------+
3. |                sin |
4. +--------------------+
5. | 0.8414709848078965 |
6. +--------------------+
7. SELECT 1 row in set (... sec)

asin(number)

Returns the arcsine of the argument.

Returns: double precision

See below for an example:

1. cr> SELECT asin(1) AS asin;
2. +--------------------+
3. |               asin |
4. +--------------------+
5. | 1.5707963267948966 |
6. +--------------------+
7. SELECT 1 row in set (... sec)

cos(number)

Returns the cosine of the argument.

Returns: double precision

See below for an example:

1. cr> SELECT cos(1) AS cos;
2. +--------------------+
3. |                cos |
4. +--------------------+
5. | 0.5403023058681398 |
6. +--------------------+
7. SELECT 1 row in set (... sec)

acos(number)

Returns the arccosine of the argument.

Returns: double precision

See below for an example:

1. cr> SELECT acos(-1) AS acos;
2. +-------------------+
3. |              acos |
4. +-------------------+
5. | 3.141592653589793 |
6. +-------------------+
7. SELECT 1 row in set (... sec)

tan(number)

Returns the tangent of the argument.

Returns: double precision

See below for an example:

1. cr> SELECT tan(1) AS tan;
2. +--------------------+
3. |                tan |
4. +--------------------+
5. | 1.5574077246549023 |
6. +--------------------+
7. SELECT 1 row in set (... sec)

cot(number)

Returns the cotangent of the argument that r

（超出体积上限，已截断）