From 6eb9c5a5657d1fe77b55cc261450f3538d35a94d Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:19:15 +0200 Subject: Adding upstream version 13.4. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/infoschema-transforms.html | 55 ++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 doc/src/sgml/html/infoschema-transforms.html (limited to 'doc/src/sgml/html/infoschema-transforms.html') diff --git a/doc/src/sgml/html/infoschema-transforms.html b/doc/src/sgml/html/infoschema-transforms.html new file mode 100644 index 0000000..9fbd782 --- /dev/null +++ b/doc/src/sgml/html/infoschema-transforms.html @@ -0,0 +1,55 @@ + +36.51. transforms

36.51. transforms

+ The view transforms contains information about the + transforms defined in the current database. More precisely, it contains a + row for each function contained in a transform (the from SQL + or to SQL function). +

Table 36.49. transforms Columns

+ Column Type +

+

+ Description +

+ udt_catalog sql_identifier +

+

+ Name of the database that contains the type the transform is for (always the current database) +

+ udt_schema sql_identifier +

+

+ Name of the schema that contains the type the transform is for +

+ udt_name sql_identifier +

+

+ Name of the type the transform is for +

+ specific_catalog sql_identifier +

+

+ Name of the database containing the function (always the current database) +

+ specific_schema sql_identifier +

+

+ Name of the schema containing the function +

+ specific_name sql_identifier +

+

+ The specific name of the function. See Section 36.41 for more information. +

+ group_name sql_identifier +

+

+ The SQL standard allows defining transforms in groups, + and selecting a group at run time. PostgreSQL does not support this. + Instead, transforms are specific to a language. As a compromise, this + field contains the language the transform is for. +

+ transform_type character_data +

+

+ FROM SQL or TO SQL +


\ No newline at end of file -- cgit v1.2.3