Skip navigation.

XQuery Reference Guide

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents Index View as PDF   Get Adobe Reader

Functions Reference

The World Wide Web (W3C) specification for XQuery supports a discrete set of functions. BEA Liquid Data for WebLogic supports a subset of those functions as built-in functions. The Liquid Data built-in functions are accessible in the Data View Builder from Builder Toolbar—>Toolbox tab—>Functions panel.

For more information on the functions described here, see also:

This section provides a complete reference of the W3C functions Liquid Data supports, as well as any extended functions Liquid Data supports. This functions reference is organized by category as follows:

 


About Liquid Data XQuery Functions

You can browse the Liquid Data XQuery functions in the Data View Builder. The functions are located in the Design tab —> Toolbox tab —> XQuery Functions. You can also make your own custom functions. This section describes the conventions used in the Liquid Data XQuery functions and describes the XQuery data types.

Naming Conventions

The xf: prefix is a W3C XML naming convention, also known as a namespace. Liquid Data supports extended functions that are enhancements to the XQuery specification, which you can recognize by their extended function prefix xfext:. For example, the full XQuery notation for an extended function is xfext:function_name. Extended functions accept standard input types, but they are limited to single values.

Liquid Data also supports extensions to XQuery data types that are designated with xsext:datatype notation. When you encounter the xsext: prefix, it means that the data type may have Liquid Data-imposed restrictions that are necessary to interface successfully with the Liquid Data Server.

The xfext: prefix identifies an extended function. The prefix identifies the type of function to you but the Data View Builder does not recognize or process the prefix.

Occurrence Indicators

An occurrence indicator indicates the number of items in a sequence. This notation usually appears on a parent node in a schema. Use these identifiers to determine the repeatability of a node.

These occurrence indicators also communicate information about the data type when they appear in a function signature. For example:

Data Types

Every data element or variable has a data type. Function parameters have data type requirements and the function result is returned as a data type. The following table describes other data types that conform to the XQuery specification. Current compliance with the W3C XQuery specification extends to XQuery 1.0 and XPath 2.0 Functions and Operators specification dated 30 April 2002. Another helpful reference is XML Schema Part 2: Datatypes.

Table 3-1 Data Types 

Data Type Name

Description

xs:anyType

Represents the most generic data type. All data types including anyAttribute, anyElement, anySimpleType, anyValue, as well as sequences, items, nodes, strings, decimals.

xsext:anyValue

A subset of xs:anyType including dateTime, boolean, string, numeric values, or any single value. Does not include anyAttribute, anyElement, item, node, sequence, or anySimpleType.

xs:boolean

A subset of xsext:anyValue. A value that supports the mathematical concept of binary-valued logic: true or false.

xs:byte

A subset of xs:short. A sequence of decimal digits (0-9) with a range of 127 to -128. If the sign is omitted, plus (+) is assumed.

Examples: -1, 0, 126, +100

xs:date

A subset of xsext:anyValue. Represents the leftmost component of dateTime YYYY-MM-DD where:

  • YYYY is the year

  • MM is the month

  • DD is the day

May be preceded by a leading minus (-) sign to indicate a negative number. If the sign is omitted, plus (+) is assumed.

May be immediately followed by a Z to indicate Coordinated Universal Time (UTC) or, to indicate the time zone (the difference between the local time and Coordinated Universal Time), immediately followed by a sign, + or -, followed by the difference from UTC represented as hh:mm.

Example:

To specify 1:20 pm on May the 31st, 1999, write: 1999-05-31.

xs:dateTime

A subset of xsext:anyValue. Represents the format YYYY-MM-DDThh:mm:ss where:

  • YYYY is the year

  • MM is the month

  • DD is the day

  • T is the date/time separator

  • hh is the hour

  • mm is the minute

  • ss is the second

May be preceded by a leading minus (-) sign to indicate a negative number. If the sign is omitted, plus (+) is assumed. Additional digits can be used to increase the precision of fractional seconds if desired (ss.ss...) with any number of digits after the decimal point is supported.

May be immediately followed by a Z to indicate Coordinated Universal Time (UTC) or, to indicate the time zone (the difference between the local time and Coordinated Universal Time), immediately followed by a sign, + or -, followed by the difference from UTC represented as hh:mm.

Example:

To specify 1:20 pm on May the 31st, 1999 EST, which is five hours behind Coordinated Universal Time (UTC), write: 1999-05-31T13:20:00-05:00.

xs:decimal

A subset of xsext:anyValue. Includes all integer types, such as xs:integer, xs:long, xs:short, xs:int, or xs:byte.

Represents a finite-length sequence of decimal digits (0-9) separated by an optional period as a decimal indicator. An optional leading sign is allowed. If the sign is omitted, plus (+) is assumed. Leading and trailing zeroes are optional. If the fractional part is zero, the period and following zeroes can be omitted.

Examples: -1.23, 12678967.543233, +100000.00, 210

xs:double

A subset of xsext:anyValue. There are no subordinate data types; however, xs:float and xs:decimal, and all derived types, can be promoted to xs:double in certain cases, such as function calls.

Represents a double precision 64-bit floating point value. Supports the special values positive and negative zero, positive and negative infinity and not-a-number (0, -0, INF, -INF and NaN).

xs:float

A subset of xsext:anyValue. There are no subordinate data types; however, xs:decimal, and all derived types, can be promoted to xs:float in certain cases, such as function calls.

Represents a single-precision 32-bit floating point value. Supports the special values positive and negative zero, positive and negative infinity and not-a-number (0, -0, INF, -INF and NaN).

xsext:item

A subset of xs:anyType. Includes xsext:anyValue and xsext:node. Excludes any sequence. Represents a list element, individual value, or attribute.

xs:int

A subset of xs:long. Represents a finite-length sequence of decimal digits (0-9). An optional leading sign is allowed. If the sign is omitted, plus (+) is assumed.

Examples: -1, 0, 12678967543233, +100000

xs:integer

A subset of xs:decimal. Represents a finite-length sequence of decimal digits (0-9). An optional leading sign is allowed. If the sign is omitted, plus (+) is assumed.

Examples: -1, 0, 12678967543233, +100000

xs:long

A subset of xs:decimal. A sequence of decimal digits (0-9) with a range of 9223372036854775807 to -9223372036854775808. If the sign is omitted, plus (+) is assumed.

Examples: -1, 0, 12678967543233, +100000

xsext:node

A subset of xsext:anyValue. A component in a tree structure that represents a data element.

xs:short

A subset of xs:int. A sequence of decimal digits (0-9) with a range of 32767 to -32768. If the sign is omitted, plus (+) is assumed.

Examples: -1, 0, 12678, +10000

xs:string

A subset of xsext:anyValue. A sequence that contains alphabetic, numeric, or special characters.

xs:time

A subset of xsext:anyValue. Represents the rightmost segment of the dateTime format where:

  • hh is the hour

  • mm is the minute

  • ss is the second

May contain an optional following time zone indicator.

Examples:

  • To indicate 1:20 pm EST, which is five hours behind Coordinated Universal Time (UTC), write: 13:20:00-05:00.

  • Midnight is 00:00:00.


 

Date and Time Patterns

You can construct date and time patterns using standard Java class symbols. The following table shows the pattern symbols you can use.

Table 3-2 Date and Time Patterns 

This Symbol

Represents This Data

Produces This Result

G

Era

AD

y

Year

1996

M

Month of year

July, 07

d

Day of the month

19

h

Hour of the day (1-12)

10

H

Hour of the day (0-23)

22

m

Minute of the hour

30

s

Second of the minute

55

S

Millisecond

978

E

Day of the week

Tuesday

D

Day of the year

27

w

Week in the year

27

W

Week in the month

2

a

am/pm marker

AM, PM

k

Hour of the day (1-24)

24

K

Hour of the day (0-11)

0

z

Time zone

Pacific Standard Time

Pacific Daylight Time


 

Repeat each symbol to match the maximum number of characters required to represent the actual value. For example, to represent 4 July 2002, the pattern is d MMMM yyyy. To represent 12:43 PM, the pattern is hh:mm a.

 


Accessor and Node Functions

Accessor and node functions operate on different types of nodes and node values. They accept single node input and return a value based on the node type. These function are not available in the XQuery functions section of the Data View Builder, but the Data View Builder will, in some circumstances, generate queries that use these functions. The functions available are:

xf:data

Returns the typed-value of each input node. This function is not available in the XQuery functions section of the Data View Builder.

Data Types

Notes

The xf:data function is available to Liquid Data, but you cannot explicitly map a node in the Data View Builder, so you therefore cannot construct a query in the Data View Builder that uses the xf:data function. In some cases, however, the Data View Builder will implicitly generate queries that use the xf:data function. The typical case when the Data View Builder generates the xf:data function is when it does not know the name of the elements at query generation time, and it uses the xf:data function in a variable expression containing wildcard characters.

If the source value is not a node, the function returns an error.

XQuery Specification Compliance

Examples

xf:document (format 1)

Returns the specified document. This function is not available in the XQuery functions section of the Data View Builder.

Data Types

Notes

The input of this version of the xf:document function is the logical name of a Liquid Data data source.

Use the xf:document function to specify an XML document. Because Liquid Data models data sources as XML documents, the XML document specified can represent a relational database, an XML file, or other data sources registered in the Liquid Data Administration Console. The xf:document function is available to Liquid Data, but you cannot explicitly map a node in the Data View Builder. In many cases, however, the Data View Builder implicitly generates queries that use the xf:document function.

Example

xf:document("My_Relational_DS")

xf:document (format 2)

Returns the specified document for the given dynamic data source. This function is not available in the XQuery functions section of the Data View Builder.

Data Types

Notes

This version of the xf:document function is used with dynamic XML and delimited file data sources (a dynamic data source is a data source in which the data file is specified at query runtime). For the first input, specify the logical name of a Liquid Data data source. For the second input, specify a URL or file (absolute path or relative to the Liquid Data Repository for the type of data source).

Use the xf:document function to specify an XML document. Because Liquid Data models data sources as XML document, the XML document specified can represent a relational database, an XML file, or other data sources registered in the Liquid Data Administration Console. The xf:document function is available to Liquid Data, but you cannot explicitly map a node in the Data View Builder. In many cases, however, the Data View Builder implicitly generates queries that use the xf:document function.

Example

xf:document("My_XML_DS", "c:\myFolder\file.xml")

xf:local-name

Returns a string value that corresponds to the local name of the specified node. This function is not available in the XQuery functions section of the Data View Builder.

Data Types

Notes

The xf:local-name function is available to Liquid Data, but you cannot explicitly map a node in the Data View Builder, so you therefore cannot construct a query in the Data View Builder that uses the xf:local-name function. In some cases, however, the Data View Builder will implicitly generate queries that use the xf:local-name function. The typical case when the Data View Builder generates the xf:local-name function is when it does not know the name of the elements at query generation time, and it uses the xf:local-name function in a variable expression containing wildcard characters.

XQuery Specification Compliance

Examples

 


Aggregate Functions

Aggregate functions process a sequence as argument and return a single value computed from values in the sequence. Except for the Count function, if the sequence contains nodes, the function extracts the value from the node and uses it in the computation. The following aggregate functions are available:

xf:avg

Returns the average of a sequence of numbers.

Data Types

Notes

If the source value contains nodes, the value of each node is extracted using the xf:data function. If an empty list occurs, it is discarded.

If the source value contains only numbers, the Avg function returns the average of the numbers, which is the sum of the source sequence divided by the count of the source sequence.

If the source value is an empty list, the function returns an empty list.

If the source value contains non-numeric data, the function returns an error.

XQuery Specification Compliance

Liquid Data requires a list of double precision values instead of a list of items.

Examples

xf:count

Returns the number of items in the sequence in an unsigned integer.

Data Types

Notes

If the source value is an empty list, the function returns an empty list.

XQuery Specification Compliance

Liquid Data returns an integer value (xs:integer) instead of an unsigned int (xs:unsignedInt) value.

Examples

xf:max

Returns the maximum value from a sequence. If there are two or more items with the same value, the specific item whose value is returned is implementation-dependent.

Data Types

Notes

If the source value contains nodes, the value of each node is extracted using the xf:data function. If an empty list occurs, it is discarded.

All values in the list must be instances of one of the following types:

For example, if the list contains items with typed values that represent both decimal values and dates, an error will occur.

The values in the sequence must have a total order:

Both of these conditions must be true; otherwise, the function returns an error.

XQuery Specification Compliance

Examples

xf:min

Returns the minimum value from a sequence of numbers. If there are two or more items with the same value, the specific item whose value is returned is implementation-dependent.

Data Types

Notes

If the source value contains nodes, the value of each node is extracted using the Data function. If an empty list occurs, it is discarded.

After extracting the values from nodes, the sequence must contain only values of a single type.

The values in the sequence must have a total order:

Both of these conditions must be true; otherwise, the function returns an error.

XQuery Specification Compliance

Examples

xf:sum

Returns the sum of a sequence of numbers.

Data Types

Notes

If the source value contains nodes, the value of each node is extracted using the Data function. If an empty list occurs, it is discarded.

If the source value contains only numbers, the Sum function returns the sum of the numbers.

If the source value contains non-numeric data, the function returns an error.

If the input sequence is empty, the function returns an empty list.

XQuery Specification Compliance

Examples

 


Boolean Functions

Boolean functions return true (1) or false(0) values. The following boolean functions are available:

xf:false

Returns the boolean value false.

Data Types

XQuery Specification Compliance

Conforms to the current specification.

Examples

xf:not

Returns true if the value of the source value is false and false if the value of the source value is true.

Data Types

XQuery Specification Compliance

Examples

xf:true

Returns the boolean value true.

Data Types

XQuery Specification Compliance

Conforms to the current specification.

Examples

 


Cast Functions

Cast functions process a source value as the argument and type cast the output to a different datatype. Type casting will typically fail if applied to more than one element. An empty list is allowed, but the result of the type casting will consist of an empty list. Type casting functions are more likely to generate exceptions at run time if the parameter cannot be converted to the corresponding type.

The following table describes Liquid Data data types that conform to the XQuery specification that you can use in type casting functions. For more information about data types, see the XQuery 1.0 and XPath 2.0 Functions and Operators specification. The following cast functions are available:

cast as xs:boolean

Converts the input to a boolean value (true or false).

If the input parameter is empty, the function returns an empty list. Otherwise, Liquid Data generates an error.

Data Types

Notes

This function uses the xf:boolean-from-string function.

XQuery Specification Compliance

Conforms to the current specification; however, Liquid Data does not accept the values "1" and "0" to represent true and false, as described in the W3C XML Schema document.

Examples

cast as xs:byte

Converts the input to a byte value.

Data Types

Notes

This function uses the xf:byte function.

This function will complete sucessfully only if the value cast is a numeric value greater than -128 or less than 128; all other values will fail.

XQuery Specification Compliance

Conforms to the current specification.

Examples

cast as xs:date

Converts the input to a date value.

Data Types

Notes

This function uses the xf:date function.

The string must contain a date in one of these formats:

where YYYY represents the year, MM represents the month (as a number), DD represents the day, hh and mm represents the number of hours and minutes that the timezone differs from GMT (UTC). Z indicates that the date is in the GMT timezone.

If the string cannot be parsed into a date value, Liquid Data generates an error.

XQuery Specification Compliance

Conforms to the current specification.

Examples

cast as xs:dateTime

Converts the input to a dateTime value.

Data Types

Notes

This function uses the xf:date function.

XQuery Specification Compliance

Conforms to the current specification.

Examples

cast as xs:decimal

Converts the input to a decimal value.

Data Types

Notes

This function uses the xf:decimal function.

XQuery Specification Compliance

Examples

cast as xs:double

Converts the input to a double precision value.

Data Types

Notes

This function uses the xf:double function.

XQuery Specification Compliance

Examples

cast as xs:float

Converts the input to a floating point value.

Data Types

Notes

This function uses the xf:float function.

XQuery Specification Compliance

Examples

cast as xs:int

Converts the input to an int value.

Data Types

Notes

This function uses the xf:int function.

XQuery Specification Compliance

Conforms to the current specification.

cast as xs:integer

Converts the input to an integer value.

Data Types

Notes

This function uses the xf:integer function.

XQuery Specification Compliance

Conforms to the current specification.

cast as xs:long

Converts the input to a long value.

Data Types

Notes

This function uses the xf:long function.

XQuery Specification Compliance

Conforms to the current specification.

cast as xs:short

Converts the input to a short value.

Data Types

Notes

This function uses the xf:short function.

XQuery Specification Compliance

Conforms to the current specification.

cast as xs:string

Converts the input to a string value.

Data Types

Notes

This function uses the xf:string function.

XQuery Specification Compliance

Examples

cast as xs:time

Converts the input to a time value.

Data Types

Notes

This function uses the xf:time function.

XQuery Specification Compliance

Conforms to the current specification.

Examples

 


Comparison Operators

XQuery has operators that are specific to comparisons operations. The following operators are available:

eq

Returns true if Parameter1 is exactly equal to Parameter2.

Data Types

Notes

This is a comparison operator that you can use as a function to compare operands.

If either operand is a node, Liquid Data extracts its typed value first, then performs a type check to ensure that the type of one operand is promotable to the other type; otherwise Liquid Data generates an error.

If either operand is an empty list, the function returns an empty list.

XQuery Specification Compliance

Examples

ge

Returns true if Parameter1 is greater than or equal to Parameter2.

Data Types

Notes

This is a comparison operator that you can use as a function to compare operands.

If either operand is a node, Liquid Data extracts its typed value first, then performs a type check to ensure that the type of one operand is promotable to the other type; otherwise Liquid Data generates an error.

If either operand is an empty list, the function returns an empty list.

XQuery Specification Compliance

Examples

See the examples for eq.

gt

Returns true if Parameter1 is greater than Parameter2.

Data Types

Notes

This is a comparison operator that you can use as a function to compare operands.

If either operand is a node, Liquid Data extracts its typed value first, then performs a type check to ensure that the type of one operand is promotable to the other type; otherwise Liquid Data generates an error.

If either operand is an empty list, the function returns an empty list.

XQuery Specification Compliance

Liquid Data does not cast xs:anySimpleType to any other supported type.

Liquid Data does not support these data types: xs:yearMonthDuration, xs:dayTimeDuration, gregorian, xs:hexBinary, xs:base64Binary, xs:anyURI, xs:QName, or xs:NOTATION values.

Examples

See the examples for the "eq" operator (previous entry in this table).

le

Returns true if Parameter1 is less than or equal to Parameter2.

Data Types

Notes

This is a comparison operator that you can use as a function to compare operands.

If either operand is a node, Liquid Data extracts its typed value first, then performs a type check to ensure that the type of one operand is promotable to the other type; otherwise Liquid Data generates an error.

If either operand is an empty list, the function returns an empty list.

XQuery Specification Compliance

Liquid Data does not cast xs:anySimpleType to any other supported type.

Liquid Data does not support these data types: xs:yearMonthDuration, xs:dayTimeDuration, gregorian, xs:hexBinary, xs:base64Binary, xs:anyURI, xs:QName, or xs:NOTATION values.

Examples

See the examples for for eq.

lt

Returns true if Parameter1 is less than or equal to Parameter2.

Data Types

Notes

This is a comparison operator that you can use as a function to compare operands.

If either operand is a node, Liquid Data extracts its typed value first, then performs a type check to ensure that the type of one operand is promotable to the other type; otherwise Liquid Data generates an error.

If either operand is an empty list, the function returns an empty list.

XQuery Specification Compliance

Liquid Data does not cast xs:anySimpleType to any other supported type.

Liquid Data does not support these data types: xs:yearMonthDuration, xs:dayTimeDuration, gregorian, xs:hexBinary, xs:base64Binary, xs:anyURI, xs:QName, or xs:NOTATION values.

Examples

See the examples for for eq.

ne

The result is false if both values are false and true if at least one of the values is true. Parameter2 is not evaluated if Parameter1 evaluates to true.

Data Types

Notes

This is a boolean operator that you can use as a function to return a true or false result. It is not a standard XQuery operator, but necessary to complete certain comparative expressions in Liquid Data.

The arguments and return type are all boolean.

If either operand is a node, Liquid Data extracts its typed value first, then performs a type check to ensure that the type of one operand is promotable to the other type; otherwise Liquid Data generates an error.

If either operand is an empty list, the function returns an empty list.

XQuery Specification Compliance

Liquid Data does not support these data types: xs:yearMonthDuration, xs:dayTimeDuration, gregorian, xs:hexBinary, xs:base64Binary, xs:anyURI, xs:QName, or xs:NOTATION values.

Examples

See the examples for eq.

 


Constructor Functions

Constructor functions process a source value as the argument. Every data element or variable has a data type. The data type determines the value that any function parameter can contain and the operations that can be performed on it. The Liquid Data supports the following type casting functions. The following constructor functions are available:

xf:boolean-from-string

Returns a boolean value of true or false from the string source value.

Data Types

Notes

If the input parameter is empty, the function returns an empty list. Otherwise, Liquid Data generates an error.

XQuery Specification Compliance

Examples

xf:byte

Constructs a byte integer value from the string source value.

Data Types

Notes

An error occurs if the source value is greater than 127 or less than -128.

Liquid Data truncates the input if it is a non-integer number.

If the number falls outside of the range of byte values, the number wraps.

If the number is an integer that falls within the range, the value is unchanged.

If the input is a string, Liquid Data tries to parse it into a byte value.

If the input is the boolean value true, the function returns 1. If it is false, it returns 0.

XQuery Specification Compliance

Examples

xf:decimal

Constructs a decimal value from the source value.

Data Types

XQuery Specification Compliance

Examples

xf:double

Constructs a double precision value from the source value.

Data Types

XQuery Specification Compliance

Examples

xf:float

Constructs a floating point value from the source value.

Data Types

XQuery Specification Compliance

Examples

xf:int

Constructs an integer value from the source value. The largest integer value is limited to a 32-bit expression.

Data Types

Notes

An error occurs if the source value is greater than 2,147,483,647 or less than -2,147,483,648. To the Liquid Data Server, the xf:int function is exactly the same as the xf:integer function.

XQuery Specification Compliance

Examples

xf:integer

Constructs an integer value from the source value. The largest integer value is limited to a 32-bit expression.

Data Types

Notes

An error occurs if the source value is greater than 2,147,483,647 or less than -2,147,483,648. To the Liquid Data Server, the xf:integer function is exactly the same as the xf:int function.

XQuery Specification Compliance

Examples

xf:long

Constructs a four-byte integer value from the source value. Use a long integer data type when the value exceeds the limitations imposed by other integer data types.

Data Types

Notes

An error occurs if the source value is greater than 9,223,372,036,854,775,807 or less than -9,223,372,036,854,775,808.

XQuery Specification Compliance

Examples

xf:short

Constructs a two-byte integer value from the source value. The largest short integer value is limited to a 16-bit expression.

Data Types

Notes

An error occurs if the source value is greater than 32,767 or less than -32,768.

XQuery Specification Compliance

Examples

xf:string

Constructs a string value from the source value. The source value can be a sequence, a node of any kind, or a simple value.

Data Types

Notes

Liquid Data accepts any simple value, but supports no other accessor types, such as a sequence or other type of node.

XQuery Specification Compliance

Examples

 


Date and Time Functions

Date and Time functions extract all or part of a dateTime expression and use it in a query. The following date and time functions are available:

xf:add-days

Adds the number of days specified by Parameter2 to the date specified by Parameter1. The value of Parameter2 may be negative.

Data Types

Notes

If Parameter1 has a timezone, it remains unchanged. The returned value is always normalized into a correct Gregorian calendar date. If either parameter is an empty list, the function returns an empty list.

XQuery Specification Compliance

Conforms to the current specification.

Examples

xf:current-dateTime

Returns the current date and time.

Data Types

No parameters required.

Returned data type: xs:dateTime

Notes

The function returns the current date and time in the current timezone.

If the function is called multiple times during the execution of a query, it returns the same value each time.

XQuery Specification Compliance

Liquid Data returns the time zone where the Liquid Data Server is running.

Example

xf:current-dateTime() can return a dateTime value such as 2002-07-25T01:00:38.812-08:00, which represents July 25th, 2002 at 1:00:38 and 812 thousandths of a second in a time zone that is offset by -8 hours from GMT (UTC).

xf:date

Takes a string (rather than dateTime) and a parameter and returns a date from a source value, which must contain a date in one of these formats:

where:

Data Types

Notes

The representation for date is the leftmost representation for dateTime: YYYY-MM-DD+hh:mm with an optional following time zone indicator (Z).

Liquid Data supports this year range: 0000-9999.

XQuery Specification Compliance

Conforms to the current specification.

Examples

xf:dateTime

Returns a dateTime value from a source value, which must contain a date and time in one of these formats:

where the following is true:

Data Types

Notes

Returns a date and time in YYYY-MM-DDT+hh:mm:ss format.

This expression can be preceded by an optional leading minus (-) sign to indicate a negative number. If the sign is omitted, positive (+) is assumed.

Use additional digits to increase the precision of fractional seconds if desired. The format ss.ss... with any number of digits after the decimal point is supported. Fractional seconds are optional.

Liquid Data supports this year range: 0000-9999.

XQuery Specification Compliance

Conforms to the current specification.

Examples

xf:get-day-from-date

Returns an integer value representing the day identified in date.

Data Types

Notes

The day value ranges from 1 to 31.

If the source value is an empty list, the function returns an empty list.

XQuery Specification Compliance

Conforms to the current specification.

Examples

xf:get-day-from-dateTime

Returns an integer value representing the day identified in dateTime.

Data Types

Notes

The day value ranges from 1 to 31.

If the source value is an empty list, the function returns an empty list.

XQuery Specification Compliance

Conforms to the current specification.

Examples

xf:get-hours-from-dateTime

Returns an integer value representing the hour identified in dateTime.

Data Types

Notes

The hour value ranges from 0 to 23.

If the source value is an empty list, the function returns an empty list.

XQuery Specification Compliance

Conforms to the current specification.

Examples

xf:get-hours-from-time

Returns an integer representing the hour identified in time.

Data Types

Notes

The hour value ranges from 0 to 23, inclusive.

If the source value is an empty list, the function returns an empty list.

XQuery Specification Compliance

Conforms to the current specification.

Examples

xf:get-minutes-from-dateTime

Returns an integer value representing the minutes identified in dateTime.

Dat