|
==Databases==
In SQL databases, a user-defined function provides a mechanism for [[extension (computing)|extending]] the functionality of the [[database server]] by adding a function that can be evaluated in SQL statements. The [[SQL:2003|SQL]] standard distinguishes between scalar and table functions. A scalar function returns only a single value (or [[null (SQL)|NULL]]), whereas a table function returns a (relational) table comprised of zero or more rows and each row with one or more columns.
User-defined functions in SQL are declared using the <code>CREATE FUNCTION</code> statement. For example, a function that converts Celsius to Fahrenheit might be declared like this:
<pre>
CREATE FUNCTION CtoF(Celsius FLOAT)
RETURNS FLOAT
RETURN (Celsius * 1.8) + 32
</pre>
Once created, a user-defined function may be used as [[expression (programming)|expressions]] in SQL statements. For example, it can be invoked where most other intrinsic functions are allowed. This also includes SELECT statements, where the function can be used against data stored in tables in the database. Conceptually, the function is evaluated once per row in such usage. For example, assume a table named ELEMENTS, with a row for each known chemical element. The table has a column named BoilingPoint for the boiling point of that element, in Celsius. This query:
<pre>
SELECT Name, CtoF(BoilingPoint)
FROM Elements
</pre>
would retrieve the name and the boiling point from each row. It invokes the CtoF user-defined function as declared above in order to convert the value in the column to a value in Fahrenheit.
Each user-defined function carries certain properties or characteristics. The SQL standard defines the following properties:
* language - defines the programming language in which the user-defined function is implemented; examples are SQL, C, or Java.
* parameter style - defines the conventions that are used to pass the function parameters and results between the implementation of the function and the database system (only applicable if language is not SQL).
* specific name - a name for the function that is unique within the database. Note that the function name does not have to be unique, considering overloaded functions.
* determinism - specifies whether the function is deterministic or not. The determinism characteristic has an influence on the [[query optimizer]] when compiling a SQL statement. The rewrite of SQL statements may not change the number of function invocations for non-deterministic functions.
* SQL-data access - tells the database management system whether the function contains no SQL statements (NO SQL), contains SQL statements but does not access any tables or views (CONTAINS SQL), reads data from tables or views (READS SQL DATA), or actually modifies data in the database (MODIFIES SQL DATA).
User-defined functions should not be confused with [[stored procedure]]s. Stored procedures allow the user to group a set of SQL commands. A procedure can accept parameters and execute its SQL statements depending on those parameters. A procedure is not an [[expression (programming)|expression]] and, thus, cannot be used like user-defined functions.
Some database management systems allow the creation of user defined functions in languages other than SQL. Mirosoft SQL Server, for example, allows the user to use .NET languages for this purpose. DB2 and Oracle support usel-defined functions written in C or Java programming languages.
==External links==
| 