Single-row Functions
No. |
Oracle |
GaussDB |
---|---|---|
1 |
Supported, with differences. |
|
2 |
Supported, with differences. |
|
3 |
Supported, with differences. |
|
4 |
Character set functions |
Not supported. |
5 |
Collation functions |
Not supported. |
6 |
Supported, with differences. |
|
7 |
Supported, with differences. |
|
8 |
Supported, with differences. |
|
9 |
Supported, with differences. |
|
10 |
Collection functions |
Not supported. |
11 |
Supported. |
|
12 |
Data mining functions |
Not supported. |
13 |
Supported, with differences. |
|
14 |
JSON functions |
Not supported. |
15 |
Supported, with differences. |
|
16 |
Supported. |
|
17 |
Supported, with differences. |
No. |
Oracle |
GaussDB |
Difference |
---|---|---|---|
1 |
ABS |
Supported. |
- |
2 |
ACOS |
Supported. |
- |
3 |
ASIN |
Supported. |
- |
4 |
ATAN |
Supported. |
- |
5 |
ATAN2 |
Supported. |
- |
6 |
BITAND |
Supported. |
- |
7 |
CEIL |
Supported. |
- |
8 |
COS |
Supported. |
- |
9 |
COSH |
Supported. |
- |
10 |
EXP |
Supported. |
- |
11 |
FLOOR |
Supported. |
- |
12 |
LN |
Supported. |
- |
13 |
LOG |
Supported. |
- |
14 |
MOD |
Supported, with differences. |
|
15 |
NANVL |
Supported, with differences. |
GaussDB: NaN cannot be obtained by directly declaring or dividing a floating-point number by 0. |
16 |
POWER |
Supported. |
- |
17 |
REMAINDER |
Supported, with differences. |
If one of the two input parameters is of the int type, the other parameter must be of the int, numeric, or literal integer type (a valid number without a decimal point, for example, '12'). |
18 |
ROUND |
Supported, with differences. |
|
19 |
SIGN |
Supported. |
- |
20 |
SIN |
Supported. |
- |
21 |
SINH |
Supported. |
- |
22 |
SQRT |
Supported. |
- |
23 |
TAN |
Supported. |
- |
24 |
TANH |
Supported, with differences. |
The returned results of integers or integers enclosed in quotation marks (for example, '12') are different. |
25 |
TRUNC |
Supported. |
- |
26 |
WIDTH_BUCKET |
Supported. |
- |
No. |
Oracle |
GaussDB |
Difference |
---|---|---|---|
1 |
CHR |
Supported, with differences. |
|
2 |
CONCAT |
Supported. |
- |
3 |
INITCAP |
Supported, with differences. |
The returned value is restricted by the database character set. As a result, the returned result is different from that in Oracle. |
4 |
LOWER |
Supported, with differences. |
|
5 |
LPAD |
Supported. |
- |
6 |
LTRIM |
Supported, with differences. |
The return value types are different. If the input is of the character data type, Oracle returns the VARCHAR2 type. If the input is of the national character set specified during database creation, Oracle returns the NVARCHAR2 type. If the input is of the LOB type, Oracle returns the LOB type. GaussDB returns the TEXT type. |
7 |
NCHR |
Supported, with differences. |
|
8 |
NLS_LOWER |
Supported, with differences. |
|
9 |
NLS_UPPER |
Supported, with differences. |
|
10 |
NLSSORT |
Supported. |
- |
11 |
REGEXP_REPLACE |
Supported, with differences. |
|
12 |
REGEXP_SUBSTR |
Supported, with differences. |
The matching rules are affected by the aformat_regexp_match parameter. For details about the affected specifications, see the REGEXP_SUBSTR function in "SQL Reference > Functions and Operators > Character Processing Functions and Operators" in Developer Guide. |
13 |
REPLACE |
Supported. |
- |
14 |
RPAD |
Supported. |
- |
15 |
RTRIM |
Supported. |
- |
16 |
SUBSTR |
Supported. |
- |
17 |
TRANSLATE |
Supported. |
- |
18 |
TRIM |
Supported. |
- |
19 |
UPPER |
Supported, with differences. |
|
20 |
INSTRB |
Supported. |
- |
No. |
Oracle |
GaussDB |
Difference |
---|---|---|---|
1 |
ASCII |
Supported, with differences. |
The return value types are different. Oracle returns the uint4 type, while GaussDB returns the int4 type. |
2 |
INSTR |
Supported. |
- |
3 |
LENGTH |
Supported. |
- |
4 |
REGEXP_COUNT |
Supported, with differences. |
|
5 |
REGEXP_INSTR |
Supported, with differences. |
The matching rules are affected by the aformat_regexp_match parameter. For details about the affected specifications, see the REGEXP_INSTR function in "SQL Reference > Functions and Operators > Character Processing Functions and Operators" in Developer Guide. |
No. |
Oracle |
GaussDB |
Difference |
---|---|---|---|
1 |
ADD_MONTHS |
Supported, with differences. |
|
2 |
CURRENT_DATE |
Supported, with differences. |
GaussDB: The nls_date_format parameter cannot be used to set the time display format. |
3 |
CURRENT_TIMESTAMP |
Supported, with differences. |
The value ranges from 0 to 9 in Oracle. The value ranges from 0 to 6 in GaussDB. The trailing zeros in microseconds are not displayed. |
4 |
DBTIMEZONE |
Supported, with differences. |
GaussDB: The timestamp API with the built-in tz cannot be called. |
5 |
EXTRACT |
Supported. |
- |
6 |
LAST_DAY |
Supported, with differences. |
The return value types are different. |
7 |
LOCALTIMESTAMP |
Supported, with differences. |
The value ranges from 0 to 9 in Oracle. The value ranges from 0 to 6 in GaussDB. The trailing zeros in microseconds are not displayed. |
8 |
MONTHS_BETWEEN |
Supported, with differences. |
The input parameter types are different. |
9 |
NEW_TIME |
Supported, with differences. |
When the first input parameter of the new_time function is a literal, the literal format and the return value type of the function are different from those in Oracle. |
10 |
NEXT_DAY |
Supported. |
- |
11 |
NUMTODSINTERVAL |
Supported, with differences. |
GaussDB: The dsinterval type is not supported. Currently, interval is used to be compatible with the dsinterval type. |
12 |
NUMTOYMINTERVAL |
Supported, with differences. |
GaussDB: The yminterval type is not supported. Currently, interval is used to be compatible with the yminterval type. |
13 |
SESSIONTIMEZONE |
Supported, with differences. |
|
14 |
SYS_EXTRACT_UTC |
Supported. |
- |
15 |
SYSDATE |
Supported, with differences. |
The return value types are different. |
16 |
TO_CHAR |
Supported, with differences. |
The fmt '5' is not included in the Oracle documents and is not adapted. |
17 |
TO_DSINTERVAL |
Supported, with differences. |
GaussDB: The dsinterval type is not supported. Currently, interval is used to be compatible with the dsinterval type. |
18 |
TO_TIMESTAMP |
Supported, with differences. |
GaussDB supports only six digits for millisecond calculation, and Oracle supports nine digits. |
19 |
TO_TIMESTAMP_TZ |
Supported, with differences. |
The timestamptz of GaussDB is equivalent to the timestampwithloacltimezone of Oracle. The type corresponding to timestamptz of Oracle is missing. The value of nls_date_language can only be ENGLISH or AMERICAN. |
20 |
TO_YMINTERVAL |
Supported, with differences. |
GaussDB: The yminterval type is not supported. Currently, interval is used to be compatible with the yminterval type. |
21 |
TZ_OFFSET |
Supported, with differences. |
When a time zone name is received as an input parameter, the types of the time zone name are less than those of Oracle. |
No. |
Oracle |
GaussDB |
Difference |
---|---|---|---|
1 |
GREATEST |
Supported, with differences. |
|
2 |
LEAST |
Supported, with differences. |
|
No. |
Oracle |
GaussDB |
Difference |
---|---|---|---|
1 |
ASCIISTR |
Supported. |
- |
2 |
CAST |
Supported, with differences. |
|
3 |
HEXTORAW |
Supported. |
- |
4 |
RAWTOHEX |
Supported. |
- |
5 |
TO_BINARY_DOUBLE |
Supported, with differences. |
GaussDB: The nlsparam parameter is not supported. |
6 |
TO_BINARY_FLOAT |
Supported, with differences. |
GaussDB: The nlsparam parameter is not supported. |
7 |
TO_BLOB |
Supported, with differences. |
|
8 |
TO_CLOB |
Supported. |
- |
9 |
TO_DATE |
Supported, with differences. |
|
10 |
TO_MULTI_BYTE |
Supported. |
- |
11 |
TO_NCHAR |
Supported, with differences. |
|
12 |
TO_NUMBER |
Supported, with differences. |
GaussDB: The nlsparam parameter is not supported. |
13 |
TO_SINGLE_BYTE |
Supported. |
- |
14 |
TREAT |
Supported, with differences. |
GaussDB: The period (.) operator cannot be used to obtain values, and the values cannot be converted to the object type. |
15 |
UNISTR |
Supported, with differences. |
GaussDB supports only UTF-8 encoding. Oracle supports UTF-8 and UTF-16 encodings. |
No. |
Oracle |
GaussDB |
Difference |
---|---|---|---|
1 |
EMPTY_BLOB |
Supported. |
- |
2 |
EMPTY_CLOB |
Supported, with differences. |
GaussDB: The CLOB type does not support the locator concept in Oracle. |
No. |
Oracle |
GaussDB |
Difference |
---|---|---|---|
1 |
EXISTSNODE |
Supported, with differences. |
If the input parameter has a namespace, aliases must be defined for both the XPath and namespace. |
2 |
EXTRACTVALUE |
Supported, with differences. |
Currently, only XPath 1.0 is supported. |
3 |
SYS_XMLAGG |
Supported, with differences. |
This is an alias of xmlagg and can be replaced with xmlagg. |
4 |
XMLAGG |
Supported. |
- |
5 |
XMLCOMMENT |
Supported. |
- |
6 |
XMLCONCAT |
Supported. |
- |
7 |
XMLELEMENT |
Supported, with differences. |
For xmlelement and xmlattributes, when the value of name is NULL, the database behavior is different from that in Oracle.
|
8 |
XMLEXISTS |
Supported, with differences. |
GaussDB input parameter is of the XML type. |
9 |
XMLFOREST |
Supported, with differences. |
GaussDB return value is of the XML type. GaussDB does not support the EVALNAME syntax. |
10 |
XMLPARSE |
Supported, with differences. |
GaussDB return value is of the XML type. GaussDB does not support the WELLFORMED syntax. |
11 |
XMLROOT |
Supported, with differences. |
GaussDB return value is of the XML type. |
12 |
JSON_OBJECT |
Supported. |
- |
13 |
XMLTABLE |
Supported, with differences. |
GaussDB: The XPath 1.0 expression is used to select data from the XML file. The default namespace cannot be declared, multiple groups of inputs and aliases cannot be obtained, the passing_clause clause of the input data cannot be omitted, and the RETURNING SEQUENCE BY REF and ( SEQUENCE ) BY REF clauses are not supported. |
14 |
GETSTRINGVAL |
Supported |
- |
15 |
GETCLOBVAL |
Supported |
- |
16 |
XMLSEQUENCE |
Supported |
- |
No. |
Oracle |
GaussDB |
Difference |
---|---|---|---|
1 |
DECODE |
Supported. |
- |
2 |
DUMP |
Supported, with differences. |
The returned results of the numeric and time types in GaussDB are inconsistent with those in Oracle due to different storage formats. In GaussDB, select dump(123); returns Typ=23 Len=4: 123,0,0,0. In Oracle, select dump(123) from dual; returns Typ=2 Len=3: 194,2,24. |
3 |
ORA_HASH |
Supported, with differences. |
GaussDB has the following behaviors:
|
4 |
VSIZE |
Supported, with differences. |
The returned results of the numeric and time types in GaussDB are inconsistent with those in Oracle due to different storage formats. In GaussDB, select vsize(999); returns 4. In Oracle, select vsize(999) from dual; returns 3. |
No. |
Oracle |
GaussDB |
Difference |
---|---|---|---|
1 |
COALESCE |
Supported. |
- |
2 |
LNNVL |
Supported. |
- |
3 |
NULLIF |
Supported. |
- |
4 |
NVL |
Supported. |
- |
5 |
NVL2 |
Supported. |
- |
No. |
Oracle |
GaussDB |
Difference |
---|---|---|---|
1 |
SYS_CONTEXT |
Supported, with differences. |
GaussDB returns NULL for unsupported parameters. The following parameters are not supported:
|
2 |
SYS_GUID |
Supported. |
- |
3 |
USER |
Supported, with differences. |
The return value types are different. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot