include built-in languages in PL lang landing page
Project: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/commit/8e27e909 Tree: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/tree/8e27e909 Diff: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/diff/8e27e909 Branch: refs/heads/develop Commit: 8e27e9093f1d27277d676386144ee895ad004f86 Parents: 504c662 Author: Lisa Owen <[email protected]> Authored: Wed Oct 5 14:34:36 2016 -0700 Committer: Lisa Owen <[email protected]> Committed: Wed Oct 5 14:34:36 2016 -0700 ---------------------------------------------------------------------- plext/UsingProceduralLanguages.html.md.erb | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/8e27e909/plext/UsingProceduralLanguages.html.md.erb ---------------------------------------------------------------------- diff --git a/plext/UsingProceduralLanguages.html.md.erb b/plext/UsingProceduralLanguages.html.md.erb index 3ffba2c..c920486 100644 --- a/plext/UsingProceduralLanguages.html.md.erb +++ b/plext/UsingProceduralLanguages.html.md.erb @@ -1,13 +1,16 @@ --- -title: Using Procedural Languages and Extensions in HAWQ +title: Using Languages and Extensions in HAWQ --- -HAWQ allows user-defined functions to be written in other languages besides SQL and C. These other languages are generically called *procedural languages* (PLs). +HAWQ supports user-defined functions created with the SQL and C built-in languages, including supporting user-defined aliases for internal functions. + +HAWQ also allows user-defined functions to be written in languages other than SQL and C. These other languages are generically called *procedural languages* (PLs). For a function written in a procedural language, the database server has no built-in knowledge about how to interpret the function's source text. Instead, the task is passed to a special handler that knows the details of the language. The handler could either do all the work of parsing, syntax analysis, execution, and so on itself, or it could serve as "glue" between HAWQ and an existing implementation of a programming language. The handler itself is a C language function compiled into a shared object and loaded on demand, just like any other C function. This chapter describes the following: +- <a href="builtin_langs.html">Using HAWQ Built-In Languages</a> - <a href="using_pljava.html">Using PL/Java</a> - <a href="using_plperl.html">Using PL/Perl</a> - <a href="using_plpgsql.html">Using PL/pgSQL</a>
