SQL::S...nctions(3pm)
π SQL::Statement::Functions π
hey bestie!! welcome to the User Contributed Perl Documentation for SQL::Statement::Functions β¨ this is your one-stop shop for everything SQL-function-coded π pull up a chair, we're getting into it
πΈ NAME πΈ
SQL::Statement::Functions β built-in & user-defined SQL functions π¦
β¨ SYNOPSIS β¨
SELECT Func(args);
SELECT * FROM Func(args);
SELECT * FROM x WHERE Funcs(args);
SELECT * FROM x WHERE y < Funcs(args);
π DESCRIPTION π
so basically this module is where the built-in functions for SQL::Parser and SQL::Statement live π and here's the slay part β every single one of them is ALSO available in any DBDs that subclass those modules (like DBD::CSV, DBD::DBM, DBD::File, DBD::AnyData, DBD::Excel, etc.) π₯
This doc covers the built-in functions AND spills all the tea on how to make your own functions to supplement the built-ins π and bestie, it's easy. If you cook up one that's generally useful, peep below for how to submit it so it can become a built-in function π
Function syntax
okay so when you use SQL::Statement/SQL::Parser directly to parse SQL, functions (built-in or user-defined, doesn't matter) can show up anywhere in a SQL statement where values, column names, table names, or predicates can go β¨ But when you use the modules through a DBD, or in any other context where the SQL is both parsed AND executed, functions can occur in the same places β EXCEPT they can not occur in the column selection clause of a SELECT statement that contains a FROM clause π
# valid for both parsing and executing
SELECT MyFunc(args);
SELECT * FROM MyFunc(args);
SELECT * FROM x WHERE MyFuncs(args);
SELECT * FROM x WHERE y < MyFuncs(args);
# valid only for parsing (won't work from a DBD)
SELECT MyFunc(args) FROM x WHERE y;
π§ User-Defined Functions π§
π« Loading User-Defined Functions π«
In addition to the built-ins, you can create any number of your own user-defined functions (UDFs) π To actually use a UDF in a script, first you have to create a perl subroutine (see below), then you make the function available to your database handle using the CREATE FUNCTION or LOAD commands:
# load a single function "foo" from a subroutine
# named "foo" in the current package
$dbh->do(" CREATE FUNCTION foo EXTERNAL ");
# load a single function "foo" from a subroutine
# named "bar" in the current package
$dbh->do(" CREATE FUNCTION foo EXTERNAL NAME bar");
# load a single function "foo" from a subroutine named "foo"
# in another package
$dbh->do(' CREATE FUNCTION foo EXTERNAL NAME "Bar::Baz::foo" ');
# load all the functions in another package
$dbh->do(' LOAD "Bar::Baz" ');
Functions themselves should follow SQL identifier naming rules π Subroutines loaded with CREATE FUNCTION can have any valid perl subroutine name. Subroutines loaded with LOAD must start with SQL_FUNCTION_ and then the actual function name π For example:
package Qux::Quimble;
sub SQL_FUNCTION_FOO { ... }
sub SQL_FUNCTION_BAR { ... }
sub some_other_perl_subroutine_not_a_function { ... }
1;
# in another package
$dbh->do("LOAD Qux::Quimble");
# This loads FOO and BAR as SQL functions.
π Creating User-Defined Functions π
UDFs are perl subroutines that return values appropriate to the context of the function in a SQL statement π
like, for example, the built-in CURRENT_TIME returns a string value, so it can be used anywhere in a SQL statement that a string value can. Here's the entire perl code for that function:
# CURRENT_TIME
#
# arguments : none
# returns : string containing current time as hh::mm::ss
#
sub SQL_FUNCTION_CURRENT_TIME {
sprintf "%02s::%02s::%02s",(localtime)[2,1,0]
}
More complex functions can make use of a bunch of arguments that get passed to functions automatically π Functions always receive these values in @_:
sub FOO {
my($self,$sth,@params);
}
The first argument, $self, is whatever class the function is defined in β not generally useful unless you have an entire module to support the function.
The second argument, $sth, is the active statement handle of the current statement. Like all active statement handles, it contains the current database handle in the {Database} attribute, so you can access the database handle from any function:
sub FOO {
my($self,$sth,@params);
my $dbh = $sth->{Database};
# $dbh->do( ...), etc.
}
In actual practice you probably want to use $sth->{Database} directly rather than making a local copy, so $sth->{Database}->do(...) π
The remaining arguments, @params, are arguments passed by users to the function, either directly or with placeholders; here's another silly example that just returns the results of multiplying the arguments passed to it:
sub MULTIPLY {
my($self,$sth,@params);
return $params[0] * $params[1];
}
# first make the function available
#
$dbh->do("CREATE FUNCTION MULTIPLY");
# then multiply col3 in each row times seven
#
my $sth=$dbh->prepare("SELECT col1 FROM tbl1 WHERE col2 = MULTIPLY(col3,7)");
$sth->execute;
#
# or
#
my $sth=$dbh->prepare("SELECT col1 FROM tbl1 WHERE col2 = MULTIPLY(col3,?)");
$sth->execute(7);
π Creating In-Memory Tables with functions π
A function can return almost anything, as long as it's an appropriate return for the context the function will be used in π In the special case of table-returning functions, the function should return a reference to an array of array references with the first row being the column names and the remaining rows the data. For example:
- create a function that returns an AoA,
sub Japh {[
[qw( id word )],
[qw( 1 Hacker )],
[qw( 2 Perl )],
[qw( 3 Another )],
[qw( 4 Just )],
]}
- make your database handle aware of the function
$dbh->do("CREATE FUNCTION 'Japh');
- Access the data in the AoA from SQL
$sth = $dbh->prepare("SELECT word FROM Japh ORDER BY id DESC");
Or here's an example that does a join on two in-memory tables:
sub Prof {[ [qw(pid pname)],[qw(1 Sue )],[qw(2 Bob)],[qw(3 Tom )] ]}
sub Class {[ [qw(pid cname)],[qw(1 Chem)],[qw(2 Bio)],[qw(2 Math)] ]}
$dbh->do("CREATE FUNCTION $_) for qw(Prof Class);
$sth = $dbh->prepare("SELECT * FROM Prof NATURAL JOIN Class");
The Prof and Class functions return tables which can be used like any SQL table π
More complex functions might do something like scrape an RSS feed, or search a file system and put the results in AoA. For example, to search a directory with SQL:
sub Dir {
my($self,$sth,$dir)=@_;
opendir D, $dir or die "'$dir':$!";
my @files = readdir D;
my $data = [[qw(fileName fileExt)]];
for (@files) {
my($fn,$ext) = /^(.*)(\.[^\.]+)$/;
push @$data, [$fn,$ext];
}
return $data;
}
$dbh->do("CREATE FUNCTION Dir");
printf "%s\n", join' ',@{ $dbh->selectcol_arrayref("
SELECT fileName FROM Dir('./') WHERE fileExt = '.pl'
")};
Obviously, that function could be expanded with File::Find and/or stat to provide more information and it could be made to accept a list of directories rather than a single directory π
Table-Returning functions are a way to turn anything that can be modeled as an AoA into a DBI data source π€―
π Built-in Functions π
β SQL-92/ODBC Compatibility β
All ODBC 3.0 functions are available except for the following:
### SQL-92 / ODBC Functions
# CONVERT / CAST - Complex to implement, but a draft is in the works.
# DIFFERENCE - Function is not clearly defined in spec and has very limited applications
# EXTRACT - Contains a FROM keyword and requires rather freeform datetime/interval expression
### ODBC 3.0 Time/Date Functions only
# DAYOFMONTH, DAYOFWEEK, DAYOFYEAR, HOUR, MINUTE, MONTH, MONTHNAME, QUARTER, SECOND, TIMESTAMPDIFF,
# WEEK, YEAR - Requires freeform datetime/interval expressions. In a later release, these could
# be implemented with the help of Date::Parse.
ODBC 3.0 functions that are implemented with differences include:
# SOUNDEX - Returns true/false, instead of a SOUNDEX code
# RAND - Seed value is a second parameter with a new first parameter for max limit
# LOG - Returns base X (or 10) log of number, not natural log. LN is used for natural log, and
# LOG10 is still available for standards compatibility.
# POSITION - Does not use 'IN' keyword; cannot be fixed as previous versions of SQL::Statement defined
# the function as such.
# REPLACE / SUBSTITUTE - Uses a regular expression string for the second parameter, replacing the last two
# parameters of the typical ODBC function
π₯ Aggregate Functions π₯
MIN, MAX, AVG, SUM, COUNT
Aggregate functions are handled elsewhere β see SQL::Parser for the docs π
πΈ Date and Time Functions πΈ
These functions can be used without parentheses β¨
CURRENT_DATE aka CURDATE
# purpose : find current date
# arguments : none
# returns : string containing current date as yyyy-mm-dd
CURRENT_TIME aka CURTIME
# purpose : find current time
# arguments : optional seconds precision
# returns : string containing current time as hh:mm:ss (or ss.sss...)
CURRENT_TIMESTAMP aka NOW
# purpose : find current date and time
# arguments : optional seconds precision
# returns : string containing current timestamp as yyyy-mm-dd hh:mm:ss (or ss.sss...)
UNIX_TIMESTAMP
# purpose : find the current time in UNIX epoch format
# arguments : optional seconds precision (unlike the MySQL version)
# returns : a (64-bit) number, possibly with decimals
π String Functions π
ASCII & CHAR
# purpose : same as ord and chr, respectively (NULL for any NULL args)
# arguments : string or character (or number for CHAR); CHAR can have any amount of numbers for a string
BIT_LENGTH
# purpose : length of the string in bits
# arguments : string
CHARACTER_LENGTH aka CHAR_LENGTH
# purpose : find length in characters of a string
# arguments : a string
# returns : a number - the length of the string in characters
COALESCE aka NVL aka IFNULL
# purpose : return the first non-NULL value from a list
# arguments : 1 or more expressions
# returns : the first expression (reading left to right)
# which is not NULL; returns NULL if all are NULL
#
CONCAT
π§ part 2 loading... π§
CONCAT πΈ
- purpose β glue 1 or more strings into one single string; it's the alt-girl alternative to the
||operator - arguments β 1 or more strings
- returns β the concatenated string
- example:
SELECT CONCAT(first_string, 'this string', ' that string')
returns "<value-of-first-string>this string that string"
note β if any argument evaluates to NULL, the returned value is NULL. no cap, that's just how she is π
CONV π¦
- purpose β convert a number X from base Y to base Z (from base 2 to 64)
- arguments β X (can be a number or a string depending on the base), Y, Z (Z defaults to
10). Valid bases for Y and Z are:2,8,10,16and64 - returns β either a string or number, in base Z
- notes β the behavioral table, bestie:
- base
2β binary, base 2 -(0,1) - base
8β octal, base 8 -(0..7) - base
10β decimal, base 10 -(0..9) - base
16β hexadecimal, base 16 -(0..9,a..f) - base
64β0-63fromMIME::Base64
- base
DECODE π
- purpose β compare the first argument against succeeding arguments at position
1 + 2N(N = 0 to (# of arguments - 2)/2), and if equal, return the value of the argument at1 + 2N + 1; if no arguments are equal, the last argument value is returned - arguments β 4 or more expressions, must be even # of arguments
- returns β the value of the argument at
1 + 2N + 1if argument1 + 2Nis equal to argument1; else the last argument value - example:
SELECT DECODE(some_column,
'first value', 'first value matched'
'2nd value', '2nd value matched'
'no value matched'
)
INSERT β¨
- purpose β string where L characters have been deleted from STR1, beginning at S, and where STR2 has been inserted into STR1, beginning at S. NULL for any NULL args.
- arguments β STR1, S, L, STR2
HEX & OCT & BIN π
- purpose β convert number X from decimal to hex/octal/binary; equiv. to
CONV(X, 10, 16/8/2) - arguments β X
LEFT & RIGHT π«Ά
- purpose β leftmost or rightmost L characters in STR, or NULL for any NULL args
- arguments β STR1, L
LOCATE aka POSITION π₯
- purpose β starting position (one-based) of the first occurrence of STR1 within STR2;
0if it doesn't occur and NULL for any NULL args - arguments β STR1, STR2, and an optional S (starting position to search)
LOWER & UPPER aka LCASE & UCASE π
- purpose β lower-case or upper-case a string
- arguments β a string
- returns β the string lower or upper cased
LTRIM & RTRIM π
- purpose β left/right counterparts for
TRIM - arguments β string
OCTET_LENGTH π
- purpose β length of the string in bytes (not characters)
- arguments β string
REGEX π
- purpose β test if a string matches a perl regular expression
- arguments β a string and a regex to match the string against
- returns β boolean value of the regex match
- example:
... WHERE REGEX(col3,'/^fun/i') ... matches rows
in which col3 starts with "fun", ignoring case
REPEAT π§
- purpose β string composed of STR1 repeated C times, or NULL for any NULL args
- arguments β STR1, C
REPLACE aka SUBSTITUTE π
- purpose β perform perl subsitution on input string
- arguments β a string and a substitute pattern string
- returns β the result of the substitute operation
- example:
... WHERE REPLACE(col3,'s/fun(\w+)nier/$1/ig') ... replaces
all instances of /fun(\w+)nier/ in col3 with the string
between 'fun' and 'nier'
SOUNDEX πΆ
- purpose β test if two strings have matching soundex codes
- arguments β two strings
- returns β true if the strings share the same soundex code
- example:
... WHERE SOUNDEX(col3,'fun') ... matches rows
in which col3 is a soundex match for "fun"
SPACE πΈ
- purpose β a string of spaces
- arguments β number of spaces
SUBSTRING π
SUBSTRING( string FROM start_pos [FOR length] )
Returns the substring starting at start_pos and extending for "length" character or until the end of the string, if no "length" is supplied. Examples:
SUBSTRING( 'foobar' FROM 4 ) # returns "bar"
SUBSTRING( 'foobar' FROM 4 FOR 2) # returns "ba"
Note: The SUBSTRING function is implemented inSQL::ParserandSQL::Statementand, at the current time, can not be over-ridden. π
SUBSTR π¦
- purpose β same as
SUBSTRING, except with comma-delimited params, instead of words (NULL for any NULL args) - arguments β string, start_pos, [length]
TRANSLATE π
- purpose β transliteration; replace a set of characters in a string with another set of characters (a la
tr///), or NULL for any NULL args - arguments β string, string to replace, replacement string
TRIM β¨
TRIM ( [ [LEADING|TRAILING|BOTH] ['trim_char'] FROM ] string )
Removes all occurrences of <trim_char> from the front, back, or both sides of a string.
BOTH is the default if neither LEADING nor TRAILING is specified.
Space is the default if no trim_char is specified.
Examples:
TRIM( string )
trims leading and trailing spaces from string
TRIM( LEADING FROM str )
trims leading spaces from string
TRIM( 'x' FROM str )
trims leading and trailing x's from string
Note: The TRIM function is implemented inSQL::ParserandSQL::Statementand, at the current time, can not be over-ridden. π
UNHEX π₯
- purpose β convert each pair of hexadecimal digits to a byte (or a Unicode character)
- arguments β string of hex digits, with an optional encoding name of the data string
Numeric Functions π’
ABS π
- purpose β find the absolute value of a given numeric expression
- arguments β numeric expression
CEILING (aka CEIL) & FLOOR π
- purpose β rounds up/down to the nearest integer
- arguments β numeric expression
EXP β
- purpose β raise e to the power of a number
- arguments β numeric expression
LOG π¦
- purpose β base B logarithm of X
- arguments β B, X or just one argument of X for base 10
LN & LOG10 π
- purpose β natural logarithm (base e) or base 10 of X
- arguments β numeric expression
MOD π
- purpose β modulus, or remainder, left over from dividing X / Y
- arguments β X, Y
POWER aka POW π
- purpose β X to the power of Y
- arguments β X, Y
RAND π
- purpose β random fractional number greater than or equal to 0 and less than the value of X
- arguments β X (with optional seed value of Y)
ROUND β¨
- purpose β round X with Y number of decimal digits (precision)
- arguments β X, optional Y defaults to
0
SIGN π
- purpose β returns
-1,0,1, NULL for negative, 0, positive, NULL values, respectively - arguments β numeric expression
SQRT π§
- purpose β square root of X
- arguments β X
TRUNCATE aka TRUNC π₯
- purpose β similar to
ROUND, but removes the decimal - arguments β X, optional Y defaults to
0
Trigonometric Functions π
All of these functions work exactly like their counterparts in Math::Trig; go there for documentation. like, genuinely, that's the assignment β¨
ACOS ACOSEC ACOSECH ACOSH ACOT ACOTAN ACOTANH ACOTH ACSC ACSCH ASEC ASECH ASIN ASINH ATAN ATANH COS COSEC COSECH COSH COT COTAN COTANH COTH CSC CSCH SEC SECH SIN SINH TAN TANH
- Takes a single parameter. All of
Math::Trig's aliases are included. π«Ά
ATAN2
- The y,x version of arc tangent.
DEG2DEG, DEG2GRAD, DEG2RAD π
- Converts out-of-bounds values into its correct range.
GRAD2DEG, GRAD2GRAD, GRAD2RAD, RAD2DEG, RAD2GRAD, RAD2RAD π
- Like their
Math::Trig's counterparts, accepts an optional 2nd boolean parameter (likeTRUE) to keep prevent range wrapping.
DEGREES, RADIANS πΈ
DEGREESandRADIANSare included for SQL-92 compatibility, and map toRAD2DEGandDEG2RAD, respectively.
PI
PIcan be used without parentheses. iconic behaviour tbh π
System Functions π₯οΈ
DBNAME & USERNAME (aka USER) π
- purpose β name of the database / username
- arguments β none
Special Utility Functions π οΈ
IMPORT π
CREATE TABLE foo AS IMPORT(?) ,{},$external_executed_sth
CREATE TABLE foo AS IMPORT(?) ,{},$AoA
RUN π
Takes the name of a file containing SQL statements and runs the statements; see SQL::Parser for documentation.
Submitting built-in functions π«Ά
If you make a generally useful UDF, why not submit it to me and have it (and your name) included with the built-in functions? Please follow the format shown in the module including a description of the arguments and return values for the function as well as an example. Send them to the dbi-dev@perl.org mailing list (see <http://dbi.perl.org>).
Thanks in advance :-). no seriously, bestie, we love a contribution π
ACKNOWLEDGEMENTS π
Dean Arnold supplied DECODE, COALESCE, REPLACE, many thanks! Brendan Byrd added in the Numeric/Trig/System functions and filled in the SQL92/ODBC gaps for the date/string functions. legends, both of them π
AUTHOR & COPYRIGHT π
Copyright (c) 2005 by Jeff Zucker: jzuckerATcpan.org Copyright (c) 2009-2020 by Jens Rehsack: rehsackATcpan.org
All rights reserved.
The module may be freely distributed under the same terms as Perl itself using either the "GPL License" or the "Artistic License" as specified in the Perl README file.
and that's a wrap, bestie π this whole page came from perl v5.30.3, dated 2020-10-23, and it lives at SQL::S...nctions(3pm) β go forth and query, you absolute main character π
β¨
π¦ where this page comes from
- debian bookworm: libsql-statement-perl 1.414-1 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- debian trixie: libsql-statement-perl 1.414-1 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- ubuntu jammy: libsql-statement-perl 1.414-1 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- ubuntu noble: libsql-statement-perl 1.414-1 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- ubuntu resolute: libsql-statement-perl 1.414-1 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- ubuntu stonking: libsql-statement-perl 1.414-1 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms