<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OpenText Analytics Database 26.2.x – Data-type-specific functions</title>
    <link>/en/sql-reference/functions/data-type-specific-functions/</link>
    <description>Recent content in Data-type-specific functions on OpenText Analytics Database 26.2.x</description>
    <generator>Hugo -- gohugo.io</generator>
    
	  <atom:link href="/en/sql-reference/functions/data-type-specific-functions/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>Sql-Reference: Collection functions</title>
      <link>/en/sql-reference/functions/data-type-specific-functions/collection-functions/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/sql-reference/functions/data-type-specific-functions/collection-functions/</guid>
      <description>
        
        
        &lt;p&gt;The functions in this section apply to collection types (arrays and sets).&lt;/p&gt;
&lt;p&gt;Some functions apply aggregation operations (such as sum) to collections. These function names all begin with APPLY.&lt;/p&gt;
&lt;p&gt;Other functions in this section operate specifically on arrays or sets, as indicated on the individual reference pages. Array functions operate on both native array values and array values in external tables.&lt;/p&gt;
&lt;h2 id=&#34;notes&#34;&gt;Notes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Arrays are 0-indexed. The first element&#39;s ordinal position in 0, second is 1, and so on. Indexes are not meaningful for sets.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Unless otherwise stated, functions operate on one-dimensional (1D) collections only. To use multidimensional arrays, you must first dereference to a 1D array type. Sets can only be one-dimensional.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;

      </description>
    </item>
    
    <item>
      <title>Sql-Reference: Date/time functions</title>
      <link>/en/sql-reference/functions/data-type-specific-functions/datetime-functions/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/sql-reference/functions/data-type-specific-functions/datetime-functions/</guid>
      <description>
        
        
        &lt;p&gt;Date and time functions perform conversion, extraction, or manipulation operations on date and time data types and can return date and time information.&lt;/p&gt;
&lt;h2 id=&#34;usage&#34;&gt;Usage&lt;/h2&gt;
&lt;p&gt;Functions that take &lt;code&gt;TIME&lt;/code&gt; or &lt;code&gt;TIMESTAMP&lt;/code&gt; inputs come in two variants:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;TIME WITH TIME ZONE&lt;/code&gt; or &lt;code&gt;TIMESTAMP WITH TIME ZONE&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code&gt;TIME WITHOUT TIME ZONE&lt;/code&gt; or &lt;code&gt;TIMESTAMP WITHOUT TIME ZONE&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For brevity, these variants are not shown separately.&lt;/p&gt;
&lt;p&gt;The + and * operators come in commutative pairs; for example, both &lt;code&gt;DATE + INTEGER&lt;/code&gt; and &lt;code&gt;INTEGER + DATE&lt;/code&gt;. We show only one of each such pair.&lt;/p&gt;
&lt;h2 id=&#34;daylight-savings-time-considerations&#34;&gt;Daylight savings time considerations&lt;/h2&gt;
&lt;p&gt;When adding an &lt;code&gt;INTERVAL&lt;/code&gt; value to (or subtracting an &lt;code&gt;INTERVAL&lt;/code&gt; value from) a &lt;code&gt;TIMESTAMP&lt;/code&gt; WITH &lt;code&gt;TIME ZONE&lt;/code&gt; value, the days component advances (or decrements) the date of the &lt;code&gt;TIMESTAMP WITH TIME ZONE&lt;/code&gt; by the indicated number of days. Across daylight saving time changes (with the session time zone set to a time zone that recognizes DST), this means &lt;code&gt;INTERVAL &#39;1 day&#39;&lt;/code&gt; does not necessarily equal &lt;code&gt;INTERVAL &#39;24 hours&#39;&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;For example, with the session time zone set to &lt;code&gt;CST7CDT&lt;/code&gt;:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;TIMESTAMP WITH TIME ZONE &amp;#39;2014-04-02 12:00-07&amp;#39; + INTERVAL &amp;#39;1 day&amp;#39;
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;produces&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;TIMESTAMP WITH TIME ZONE &amp;#39;2014-04-03 12:00-06&amp;#39;
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Adding &lt;code&gt;INTERVAL &#39;24 hours&#39;&lt;/code&gt; to the same initial &lt;code&gt;TIMESTAMP WITH TIME ZONE&lt;/code&gt; produces&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;TIMESTAMP WITH TIME ZONE &amp;#39;2014-04-03 13:00-06&amp;#39;,
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;This result occurs because there is a change in daylight saving time at &lt;code&gt;2014-04-03 02:00&lt;/code&gt; in time zone &lt;code&gt;CST7CDT&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id=&#34;datetime-functions-in-transactions&#34;&gt;Date/time functions in transactions&lt;/h2&gt;
&lt;p&gt;Certain date/time functions such as 
&lt;code&gt;&lt;a href=&#34;../../../../en/sql-reference/functions/data-type-specific-functions/datetime-functions/current-timestamp/#&#34;&gt;CURRENT_TIMESTAMP&lt;/a&gt;&lt;/code&gt; and 
&lt;code&gt;&lt;a href=&#34;../../../../en/sql-reference/functions/data-type-specific-functions/datetime-functions/now-datetime/#&#34;&gt;NOW&lt;/a&gt;&lt;/code&gt; return the start time of the current transaction; for the duration of that transaction, they return the same value. Other date/time functions such as 
&lt;code&gt;&lt;a href=&#34;../../../../en/sql-reference/functions/data-type-specific-functions/datetime-functions/timeofday/#&#34;&gt;TIMEOFDAY&lt;/a&gt;&lt;/code&gt; always return the current time.&lt;/p&gt;
&lt;h2 id=&#34;see-also&#34;&gt;See also&lt;/h2&gt;
&lt;a href=&#34;../../../../en/sql-reference/functions/formatting-functions/template-patterns-datetime-formatting/#&#34;&gt;Template patterns for date/time formatting&lt;/a&gt;

      </description>
    </item>
    
    <item>
      <title>Sql-Reference: IP address functions</title>
      <link>/en/sql-reference/functions/data-type-specific-functions/ip-address-functions/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/sql-reference/functions/data-type-specific-functions/ip-address-functions/</guid>
      <description>
        
        
        &lt;p&gt;IP functions perform conversion, calculation, and manipulation operations on IP, network, and subnet addresses.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Sql-Reference: Sequence functions</title>
      <link>/en/sql-reference/functions/data-type-specific-functions/sequence-functions/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/sql-reference/functions/data-type-specific-functions/sequence-functions/</guid>
      <description>
        
        
        &lt;p&gt;The sequence functions provide simple, multiuser-safe methods for obtaining successive sequence values from sequence objects.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Sql-Reference: String functions</title>
      <link>/en/sql-reference/functions/data-type-specific-functions/string-functions/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/sql-reference/functions/data-type-specific-functions/string-functions/</guid>
      <description>
        
        
        &lt;p&gt;String functions perform conversion, extraction, or manipulation operations on strings, or return information about strings.&lt;/p&gt;
&lt;p&gt;This section describes functions and operators for examining and manipulating string values. Strings in this context include values of the types CHAR, VARCHAR, BINARY, and VARBINARY.&lt;/p&gt;
&lt;p&gt;Unless otherwise noted, all of the functions listed in this section work on all four data types. As opposed to some other SQL implementations, OpenText™ Analytics Database keeps CHAR strings unpadded internally, padding them only on final output. So converting a CHAR(3) &#39;ab&#39; to VARCHAR(5) results in a VARCHAR of length 2, not one with length 3 including a trailing space.&lt;/p&gt;
&lt;p&gt;Some of the functions described here also work on data of non-string types by converting that data to a string representation first. Some functions work only on character strings, while others work only on binary strings. Many work for both. BINARY and VARBINARY functions ignore multibyte UTF-8 character boundaries.&lt;/p&gt;
&lt;p&gt;Non-binary character string functions handle normalized multibyte UTF-8 characters, as specified by the Unicode Consortium. Unless otherwise specified, those character string functions for which it matters can optionally specify whether VARCHAR arguments should be interpreted as octet (byte) sequences, or as (locale-aware) sequences of UTF-8 characters. This is accomplished by adding &amp;quot;USING OCTETS&amp;quot; or &amp;quot;USING CHARACTERS&amp;quot; (default) as a parameter to the function.&lt;/p&gt;
&lt;p&gt;Some character string functions are &lt;a class=&#34;glosslink&#34; href=&#34;../../../../en/glossary/stable-functions/&#34; title=&#34;See also Immutable (invariant) functions.&#34;&gt;stable&lt;/a&gt; because in general UTF-8 case-conversion, searching and sorting can be locale dependent. Thus, LOWER is stable, while LOWERB is &lt;a class=&#34;glosslink&#34; href=&#34;../../../../en/glossary/immutable-invariant-functions/&#34; title=&#34;&#34;&gt;immutable&lt;/a&gt;. The USING OCTETS clause converts these functions into their &amp;quot;B&amp;quot; forms, so they become immutable. If the locale is set to collation=binary, which is the default, all string functions—except CHAR_LENGTH/CHARACTER_LENGTH, LENGTH, SUBSTR, and OVERLAY—are converted to their &amp;quot;B&amp;quot; forms and so are immutable.&lt;/p&gt;
&lt;p&gt;BINARY implicitly converts to VARBINARY, so functions that take VARBINARY arguments work with BINARY.&lt;/p&gt;
&lt;p&gt;For other functions that operate on strings (but not VARBINARY), see &lt;a href=&#34;../../../../en/sql-reference/functions/match-and-search-functions/regular-expression-functions/#&#34;&gt;Regular expression functions&lt;/a&gt;.&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Sql-Reference: URI functions</title>
      <link>/en/sql-reference/functions/data-type-specific-functions/uri-functions/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/sql-reference/functions/data-type-specific-functions/uri-functions/</guid>
      <description>
        
        
        &lt;p&gt;The functions in this section follow the RFC 3986 standard for percent-encoding a Universal Resource Identifier (URI).&lt;/p&gt;

      </description>
    </item>
    
    <item>
      <title>Sql-Reference: UUID functions</title>
      <link>/en/sql-reference/functions/data-type-specific-functions/uuid-functions/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/sql-reference/functions/data-type-specific-functions/uuid-functions/</guid>
      <description>
        
        
        &lt;p&gt;Currently, OpenText™ Analytics Database provides one function to support &lt;a href=&#34;../../../../en/sql-reference/data-types/uuid-data-type/&#34;&gt;UUID&lt;/a&gt; data types, 
&lt;code&gt;&lt;a href=&#34;../../../../en/sql-reference/functions/data-type-specific-functions/uuid-functions/uuid-generate/#&#34;&gt;UUID_GENERATE&lt;/a&gt;&lt;/code&gt;.&lt;/p&gt;

      </description>
    </item>
    
  </channel>
</rss>
