Platform and Client Compatibility

Many platforms use the database system. External compatibility of the database system provides a lot of convenience for platforms.

convert_string_to_digit

Parameter description: Specifies the implicit conversion priority, which determines whether to preferentially convert strings into numbers.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

• on indicates that strings are preferentially converted into numbers.
• off indicates that strings are not preferentially converted into numbers.

Default value: on

NOTICE: Adjusting this parameter will change the internal data type conversion rule and cause unexpected behavior. Exercise caution when performing this operation.

nls_timestamp_format

Parameter description: Specifies the default timestamp format.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: a string

Default value: DD-Mon-YYYY HH:MI:SS.FF AM

group_concat_max_len

Parameter description: This parameter is used with the function GROUP_CONCAT to limit the length of its return value and truncate it if it is too long.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: 0-9223372036854775807

Default value: 1024

Note: The maximum length that can be returned is 1073741823, beyond which there will be an out of memory error.

max_function_args

Parameter description: Specifies the maximum number of parameters allowed for a function.

This parameter is a fixed INTERNAL parameter and cannot be modified.

Value range: an integer.

Default value: 8192

transform_null_equals

Parameter description: Specifies whether expressions of the form expr = NULL (or NULL = expr) are treated as expr IS NULL. They return true if expr evaluates to NULL, and false otherwise.

• The correct SQL-standard-compliant behavior of expr = NULL is to always return null (unknown).
• Filtered forms in Microsoft Access generate queries that appear to use expr = NULL to test for null values. If you enable this parameter, you can use this interface to access the database.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 Methods for setting GUC parameters.

Value range: Boolean

• on indicates expressions of the form expr = NULL (or NULL = expr) are treated as expr IS NULL.
• off indicates expr = NULL always returns NULL.

Default value: off

NOTE: New users are always confused about the semantics of expressions involving NULL values. Therefore, off is used as the default value.

support_extended_features

Parameter description: Specifies whether extended database features are supported.

This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 2 Methods for setting GUC parameters.

Value range: Boolean

• on indicates that extended database features are supported.
• off indicates that extended database features are not supported.

Default value: off

sql_compatibility

Parameter description: Specifies the type of mainstream database with which the SQL syntax and statement behavior of the database is compatible.

This parameter is an INTERNAL parameter. It can be viewed but cannot be modified.

Value range: enumerated values

• A indicates that the database is compatible with the O database.
• B indicates that the database is compatible with the MY database.
• C indicates that the database is compatible with the TD database.
• PG indicates that the database is compatible with the PostgreSQL database.

Default value: A

NOTICE:

• This parameter can be set only by dbcompatibility when you run the CREATE DATABASE command to create a database.
• In the database, this parameter must be set to a specific value. It can be set to A or B and cannot be changed randomly. Otherwise, the setting is not consistent with the database behavior.

b_format_behavior_compat_options

Parameter description: Database B mode compatibility behavior configuration items, the value of this parameter consists of several configuration items separated by commas.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 Methods for setting GUC parameters.

Value range: String

Default value: ""

Note:

• Currently only supported Table 1 Compatibility B Mode Configuration Items.
• When configuring multiple compatibility configurations, adjacent configurations are separated by commas, e.g.: set b_format_behavior_compat_options='enable_set_variables,set_session_transaction';

Table 1 Compatibility B Mode Configuration Items

Configuration Item	Compatibility Behavior
enable_set_variables	The set syntax enhances control switch. - When this configuration is not set, the set custom variable, set [global |session] syntax is not supported. - Setting this configuration supports the above syntax in B-compatible mode, e.g. set @v1 = 1;。
set_session_transaction	set session transaction control switch. - When this configuration is not set, set session transaction is equivalent to set local transaction. - When this configuration is set, B-compatible mode is supported using the above syntax to modify the current session transaction characteristics.
enable_modify_column	ALTER TABLE MODIFY semantic control switch. - Without this configuration, “ALTER TABLE table_name MODIFY column_name data_type;” modifies only the data type of the column. - When setting this configuration, “ALTER TABLE table_name MODIFY column_name data_type;” modifies the entire column definition.
default_collation	Default character order forward compatibility switch. - When this configuration is not set, the field is in default character order when the character set or character order of the character type field is not explicitly specified and the table-level character order is also empty. - When this configuration is set, the character order of the character type field inherits the table-level character order when the table-level character order is not empty, and is set to the default character order corresponding to the database code when it is empty.

enable_set_variables_b_format

Parameter description: Specifies whether the function of customizing user variables is supported in the MY-compatible database.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

• on indicates that user variables can be customized in the MY-compatible database.
• off indicates that user variables cannot be customized in the MY-compatible database.

behavior_compat_options

Parameter description: Specifies database compatibility behavior. Multiple items are separated by commas (,).

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: a string

Default value: empty

NOTE:

• Multiple items are separated by commas (,), for example, set behavior_compat_options='end_month_calculate,display_leading_zero';.

The currently supported compatibility configuration items and their behavioral controls are listed below:

• display_leading_zero

  Specifies how floating point numbers are displayed.

  • If this item is not specified, for a decimal number between -1 and 1, the 0 before the decimal point is not displayed. For example:

    MogDB=# select 0.1231243 as a, 0.1231243::numeric as b,0.1231243::integer(10,3) as c, length(0.1242343) as d;
        a     |    b     |  c   | d
    ----------+----------+------+---
     .1231243 | .1231243 | .123 | 8
    (1 row)

  • If this item is specified, for a decimal number between -1 and 1, the 0 before the decimal point is displayed. For example:

    MogDB=# select 0.1231243 as a, 0.1231243::numeric as b,0.1231243::integer(10,3) as c, length(0.1242343) as d;
         a     |     b     |   c   | d
    -----------+-----------+-------+---
     0.1231243 | 0.1231243 | 0.123 | 9
    (1 row)

• end_month_calculate

  Specifies the calculation logic of the add_months function.

  Assume that the two parameters of the add_months function are param1 and param2, and that the month of param1 and param2 is result.

  • If this item is not specified, and the Day of param1 indicates the last day of a month shorter than result, the Day in the calculation result will equal that in param1. For example:

    MogDB=# select add_months('2018-02-28',3) from sys_dummy;
    add_months
    \---------------------\
    2018-05-28 00:00:00
    (1 row)

  • If this item is specified, and the Day of param1 indicates the last day of a month shorter than result, the Day in the calculation result will equal that in result. For example:

    MogDB=# select add_months('2018-02-28',3) from sys_dummy;
    add_months
    \---------------------\
    2018-05-31 00:00:00
    (1 row)

• compat_analyze_sample

  Specifies the sampling behavior of the ANALYZE operation. If this item is specified, the sample collected by the ANALYZE operation will be limited to around 30,000 records, DBnode memory consumption and maintaining the stability of ANALYZE.

• bind_schema_tablespace

  Binds a schema with the tablespace with the same name. If a tablespace name is the same as sche_name, default_tablespace will also be set to sche_name if search_path is set to sche_name.

• bind_procedure_searchpath

  Specifies the search path of the database object for which no schema name is specified.

  If no schema name is specified for a stored procedure, the search is performed in the schema to which the stored procedure belongs.

  If the stored procedure is not found, the following operations are performed:

  • If this item is not specified, the system reports an error and exits.
  • If this item is specified, the search continues based on the settings of search_path. If the issue persists, the system reports an error and exits.

• correct_to_number

  Controls the compatibility of the to_number() result.

  If this item is specified, the result of the to_number() function is the same as that of PG11. Otherwise, the result is the same as that of the O database.

• unbind_divide_bound

  Controls the range check on the result of integer division.

  If this item is specified, you do not need to check the range of the division result. For example, the result of INT_MIN/(-1) can be INT_MAX +1. If this item is not specified, an out-of-bounds error is reported because the result is greater than INT_MAX.

• return_null_string

  Specifies how to display the empty result (empty string ") of the lpad() and rpad() functions.

  If this item is not specified, the empty string is displayed as NULL.

  MogDB=# select length(lpad('123',0,'*')) from sys_dummy;
  length
  \--------\
  (1 row)

  If this item is specified, the empty string is displayed as single quotation marks (").

  MogDB=# select length(lpad('123',0,'*')) from sys_dummy;
  length
  \--------\
  0
  (1 row)

• compat_concat_variadic

  Specifies the compatibility of variadic results of the concat() and concat_ws() functions.

  If this item is specified and a concat function has a parameter of the variadic type, different result formats in O and Teradata are retained. If this item is not specified and a concat function has a parameter of the variadic type, the result format of O is retained for both O and Teradata. This option has no effect on MY because MY has no variadic type.

• merge_update_multi

  When MERGE INTO… WHEN MATCHED THEN UPDATE (see MERGE INTO) and INSERT… ON DUPLICATE KEY UPDATE (see INSERT) are used, control the UPDATE behavior if a piece of target data in the target table conflicts with multiple pieces of source data.

  If this item is specified and the preceding scenario exists, the system performs multiple UPDATE operations on the conflicting row. If this item is not specified and the preceding scenario exists, an error is reported, that is, the MERGE or INSERT operation fails.

• plstmt_implicit_savepoint

  Controls whether the execution of update statements in a procedure has separate sub-transactions.

  If this configuration item is set, implicit savepoints are turned on before each update statement in the procedure, and the default fallback in the EXCEPTION block is to the most recent savepoint, thus ensuring that only changes to failed statements are fallbacked. This option is for compatibility with the EXCEPTION behavior of the O database.

• hide_tailing_zero

  Numeric shows the configuration item. If this parameter is not set, numeric shows the configuration item based on the specified precision. When this parameter is set, hide "0" at the end of the decimal point.

  MogDB=# set behavior_compat_options='hide_tailing_zero';
  MogDB=# select cast(123.123 as numeric(15,10)) as a, to_char(cast(123.123 as numeric(15,10)), '999D999999');
      a    | to_char
  ---------+----------
   123.123 |  123.123
  (1 row)
  MogDB=# set behavior_compat_options='';
  MogDB=# select cast(123.123 as numeric(15,10)) as a, to_char(cast(123.123 as numeric(15,10)), '999D999999');
         a        |   to_char
  ----------------+-------------
   123.1230000000 |  123.123000
  (1 row)

• rownum_type_compat

  Specifies the ROWNUM type. The default value is INT8. After this parameter is specified, the value is changed to NUMERIC.

• aformat_null_test

  Determines the logic for checking whether the row type is not null. When this parameter is set, if a column in a row is not null, true is returned.

  When this parameter is not set, if all columns in a row are not null, true is returned.

• aformat_regexp_match

  Determines the matching behavior of regular expression functions.

  When this parameter is set and sql_compatibility is set to A or B, the options supported by the flags parameter of the regular expression are changed as follows:

  1. By default, the character '\n' cannot be matched.

  2. When flags contains the n option, the character '\n' can be matched.

  3. The regexp_replace(source, pattern replacement) function replaces all matching substrings.

  4. regexp_replace(source, pattern, replacement, flags) returns null when the value of flags is “ or null.

  Otherwise, the meanings of the options supported by the flags parameter of the regular expression are as follows:

  1. By default, the character '\n' can be matched.
  2. The n option in flags indicates that the multi-line matching mode is used.
  3. The regexp_replace(source, pattern replacement) function replaces only the first matched substring.
  4. If the value of flags is “ or null, the return value of regexp_replace(source, pattern, replacement, flags) is the character string after replacement.

• compat_cursor

  Determines the compatibility behavior of implicit cursor states. If this parameter is set and the O compatibility mode is used, the effective scope of implicit cursor states (SQL %FOUND, SQL %NOTFOUND, SQL %ISOPNE and SQL %ROWCOUNT) are extended only the currently executed function to all subfunctions invoked by this function.

• proc_outparam_override

  Controls the overloading behavior of the out parameter of a procedure. If this parameter is turned on, the procedure can be called normally if only the out parameter is different. When this option is set, a function or procedure that contains an out parameter must explicitly call the out parameter.

  Whether a function or procedure contains an out parameter can be seen by \df function name, for example:

  MogDB=# \df DBE_PERF.get_global_bgwriter_stat
  List of functions
  -[ RECORD 1 ]-------+----------------------------------------------------------------------
  Schema              | dbe_perf
  Name                | get_global_bgwriter_stat
  Result data type    | SETOF record
  Argument data types | OUT node_name name, OUT checkpoints_timed bigint, OUT checkpoints_req bigint, OUT checkpoint_write_time double precision, OUT checkpoint_sync_time double precision, OUT buffers_checkpoint bigint, OUT buffers_clean bigint, OUT maxwritten_clean bigint, OUT buffers_backend bigint, OUT buffers_backend_fsync bigint, OUT buffers_alloc bigint, OUT stats_reset timestamp with time zone
  Type                | normal
  fencedmode          | f
  propackage          | f
  prokind             | f

  The out/inout parameter needs to be passed as a variable, not a constant; when overriding is turned off, the out parameter can be called without explicitly under the perform operation.

  The description of the proc_outparam_override option and the behavior of the perform operation is as follows:

  1. When the proc_outparam_override option is turned off, for the out parameter, the form does not support passing in a constant, and must pass in a variable; for the inout parameter, the form supports passing in a constant, the reason is that the role of the form is to ignore the out parameter, and at this time passing a constant to the inout parameter actually passes a constant to the in parameter. The reason for this is that the purpose of the form is to ignore the out parameter.

  2. When you turn on the proc_outparam_override option, the form supports passing variables and constants to the out parameter, but it will report an error when you pass a constant, because the out parameter needs a variable to receive its value, and you can't assign a value to a constant when you pass a constant, so you need to pass a variable. The reason is that the out parameter needs a variable to receive its value, and when you pass in a constant, you can no longer assign a value to the constant.

• proc_implicit_for_loop_variable

  Determines the behavior of the FOR_LOOP query statement in a stored procedure.When this parameter is set, if rec has been defined in the FOR rec IN query LOOP statement, the defined rec variable is not reused and a new variable is created. Otherwise, the defined rec variable is reused and no new variable is created.

• allow_procedure_compile_check

  Determines the compilation check of the SELECT and OPEN CURSOR statements in a stored procedure. If this parameter is set, when the SELECT, OPEN CURSOR FOR, CURSOR %rowtype, or for rec in statement is executed in a stored procedure, the stored procedure cannot be created if the queried table does not exist, and the compilation check of the trigger function is not supported. If the queried table exists, the stored procedure is successfully created.

• char_coerce_compat

  Determines the behavior when char(n) types are converted to other variable-length string types. By default, spaces at the end are omitted when the char(n) type is converted to other variable-length string types. After this parameter is enabled, spaces at the end are not omitted during conversion. In addition, if the length of the char(n) type exceeds the length of other variable-length string types, an error is reported. This parameter is valid only when sql_compatibility is set to A.

• truncate_numeric_tail_zero

  numeric displays the configuration items. When this option is not set, the default precision of the numeric is displayed. When this item is set, all scenarios outputting numeric will hide the last zero after the decimal point, except for the case of to_char(numeric, format) which displays the set precision. for example:

  MogDB=# set behavior_compat_options='truncate_numeric_tail_zero';
  MogDB=# select cast(123.123 as numeric(15,10)) as a, to_char(cast(123.123 as numeric(15,10)), '999D999999');
      a    |   to_char
  ---------+-------------
   123.123 |  123.123000
  (1 row)
  MogDB=# set behavior_compat_options='';
  MogDB=# select cast(123.123 as numeric(15,10)) as a, to_char(cast(123.123 as numeric(15,10)), '999D999999');
         a        |   to_char
  ----------------+-------------
   123.1230000000 |  123.123000
  (1 row)

• pgformat_substr

  Controls the performance of substr(str, from, for) in different scenarios. By default, if the value of from is less than 0, substr counts from the end of the string. If the value of for is less than 1, substr returns NULL. After this parameter is enabled, if the value of from is less than 0, substr counts from the first (-from + 1) bit of the character string. If the value of for is less than 0, substr reports an error. This parameter is valid only when sql_compatibility is set to PG.

• allow_orderby_undistinct_column

  If the compatibility mode is B, when this parameter is enabled, the select statement supports order by followed by columns that are not in distinct. For example: select distinct a from test order by b;

  Note: This parameter only supports distinct, does not support distinct on, and when the DOLPHIN plugin exists does not take effect, the function is transferred to the dolphin.sql_mode parameter control. dolphin.sql_mode is equivalent to enable this option when you do not set the sql_mode_full_group option.

• select_into_return_null

  In B or PG compatibility mode, with this parameter enabled, the procedure statement SELECT select_expressions INTO [STRICT] target FROM ... allows variables to be assigned a NULL value if STRICT is not specified and the query result is null.

• convert_string_digit_to_numeric

  Controls whether numeric constants represented as strings in a table are converted to numeric types for comparison.

  MogDB=# create table test1(c1 int, c2 varchar);
  MogDB=# insert into test1 values(2, '1.1');
  MogDB=# set behavior_compat_options = '';
  MogDB=# select * from test1 where c2 > 1;
  ERROR:  invalid input syntax for type bigint: "1.1"
  MogDB=# set behavior_compat_options = 'convert_string_digit_to_numeric';
  MogDB=# select * test1 from where c2 > 1;
   c1 | c2
  ----+-----
    2 | 1.1
  (1 row)

• plsql_security_definer

  When this parameter is enabled, the procedure is created with definer privileges by default.

• skip_insert_gs_source

  When this parameter is enabled, PL/SQL objects are no longer inserted into the DBE_PLDEVELOPER.gs_source table when they are created.

• compat_sort_group_column

  When this parameter is enabled, the behavior of the GROUP/ORDER BY clause is consistent with Oracle and the constants no longer affect the GROUP/ORDER BY result set. This parameter takes effect only when the sql_compatibility parameter value is A.

• sql_implicit_savepoint

  This option is used to control whether to roll back the entire transaction when a single SQL error occurs in the transaction. When this option is set, a single SQL error in a transaction will not affect the commit of other SQL, and the commit will retain the results of the correctly executed SQL. This option is only available in A-compatible mode.

• accept_empty_str

  In A-compatible mode, when this parameter is disabled, MogDB will treat the empty string as NULL; otherwise, it will accept the empty string normally. Example:

  MogDB=# set behavior_compat_options='accept_empty_str';
  MogDB=# select '' is null;
   ?column?
  ----------
   f
  (1 row)
  MogDB=# set behavior_compat_options='';
  MogDB=# select '' is null;
   ?column?
  ----------
   t
  (1 row)

• set_procedure_current_schema

  If this parameter is enabled and the compiled function (including the function in the package) or procedure has caller privileges, set the search path of the function (including the function in the package) or procedure to the current_schema at the time of execution. The current_schema at the time of execution.

• compat_oracle_txn_control

  • Configure this option to enable select to auto-commit transactions when the driver is in non-autocommit mode.
  • If the driver is in autocommit mode (autocommit = on), enabling this option will cause the driver's autocommit mode not to take effect when the driver version is JDBC 5.0.0.6/5.0.0.7, Psycopg2 5.0.0.4, or ODBC 5.0.0.2. Subsequent versions of the driver will resolve this conflict. The temporary solution is to disable this parameter in the driver connection string.
  • The compat_oracle_txn_control option is not allowed to be modified by set behavior_compat_options after JDBC 5.0.0.8 and Psycopg2 5.0.0.5.
  • select does not auto-commit after JDBC setSavepoint.

• bpchar_coerce_compat

  Control bpchar and text operations to implicitly convert text to bpchar, so that bpchar_col = 'xxx'::text conditions can be directly applied to indexes or partitioned cuts to improve query efficiency.

• allow_like_indexable

  Configuring this option automatically creates indexes that support fuzzy matching (introduced since version 5.0.4).

plsql_compile_check_options

Parameter description: Database compatibility behavior configuration items, the value of this parameter consists of several configuration items separated by commas.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 Methods for setting GUC parameters.

Value range: String

Default value: ""

Note:

• Only the Table 2 compatibility configuration item is currently supported.
• When configuring multiple compatibility configuration items, adjacent configuration items are separated by commas. For example: set plsql_compile_check_options='for_loop,outparam';

Table 2 compatibility configuration item

Configuration Item	Compatibility Behavior
for_loop	When this item is set to control the behavior of FOR_LOOP query statements in stored procedures, if rec is already defined in a FOR rec IN query LOOP statement, the rec variable already defined is not reused and a new variable is created. Otherwise, the already defined rec variable is reused and no new variable is created. (Same as proc_implicit_for_loop_variable, with subsequent wrap-up)
outparam	The out overload condition has an overloaded function; the out out reference constants will be checked, prohibiting the out out reference from being a constant to report an error.

td_compatible_truncation

Parameter description: Specifies whether to enable features compatible with a Teradata database. You can set this parameter to on when connecting to a database compatible with the TD database, so that when you perform the INSERT operation, overlong strings are truncated based on the allowed maximum length before being inserted into char- and varchar-type columns in the target table. This ensures all data is inserted into the target table without errors reported.

NOTE: The string truncation function cannot be used if the INSERT statement includes a foreign table. If inserting multi-byte character data (such as Chinese characters) to database with the character set byte encoding (SQL_ASCII, LATIN1), and the character data crosses the truncation position, the string is truncated based on its bytes instead of characters. Unexpected result will occur in tail after the truncation. If you want correct truncation result, you are advised to adopt encoding set such as UTF8, which has no character data crossing the truncation position.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 Methods for setting GUC parameters.

Value range: Boolean

• on indicates overlong strings are truncated.
• off indicates overlong strings are not truncated.

Default value: off

uppercase_attribute_name

Parameter description: Sets the column names to be returned to the client in uppercase. This parameter is restricted to A-compatible mode and centralized environments.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

• on enables the column name to be returned to the client in uppercase.
• off disable the column name to be returned to the client in uppercase.

Default value: off

lastval_supported

Parameter description: Specifies whether to enable the lastval function.

This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

• on indicates that the lastval function is supported. Additionally, the nextval function does not support push-down.
• off indicates that the lastval function is not supported. Additionally, the nextval function supports push-down.

Default value: off

enable_custom_parser

This parameter is not supported in the current version.

enable_date_operator_sub_oracle

Parameter description: Controls whether the subtraction of two date type fields is enabled to return a numeric type result indicating the number of days between the two dates.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

• on means the operator that uses two dates subtracted as numeric.
• off means to use MogDB's original processing method, the two dates are subtracted by the Interval operator.

Default value: off

proc_inparam_immutable

Parameter description: Controls whether package constants are used as default values for function or procedure entry parameters. Applies to A-compatible mode.

This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

• on: MogDB entry parameter only IN type can use default value, and FUNCTION/PROCEDURE can not modify the entry parameter, consistent with ORACLE. Modification of the value of the PACKAGE variable affects the behavior of the function entry parameter and Oracle to maintain consistency.
• off: does not support package constants as default values for function or procedure entry parameters.

Default value: on

ora_dblink_col_case_sensitive

Parameter description: Controls whether Oracle dblink columns are case-sensitive. The default is case insensitive.

This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

Default value: off

enable_mergeinto_subqueryalias

Parameter description: Controls whether a target table alias can be used when the source table of merge into using is a subquery in A mode.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

• on means that the target table alias can be used
• off means you cannot use the target table alias.

Default value: off

enable_multitable_update

Parameter description: MogDB only supports multi-table update operation in B mode by default, enable this parameter to support using multi-table update function in A mode.

This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 GUC parameters.

Value range: Boolean

• on indicates support for using the multi-table update feature in A-mode.
• off indicates that the multi-table update function is not supported in A-mode.

Default value: off