Dictionary Views Related to MLE JavaScript Environments

Details about MLE environments are available in these families of views: USER_MLE_ENVS and USER_MLE_ENV_IMPORTS.

In addition to the USER prefix, these views exist in all namespaces: CDB, DBA, ALL, and USER.

Topics

• USER_MLE_ENVS
  The USER_MLE_ENVS view lists all MLE environments available to you along with the defined language options.
• USER_MLE_ENV_IMPORTS
  The [USER | ALL | DBA | CDB]_MLE_ENV_IMPORTS family of views lists imported modules.

USER_MLE_ENVS

The USER_MLE_ENVS view lists all MLE environments available to you along with the defined language options.

For more information about *_MLE_ENVS, see Oracle AI Database Reference.

Example 3-16 List Available MLE Environments Using USER_MLE_ENVS

SELECT ENV_NAME, LANGUAGE_OPTIONS
FROM USER_MLE_ENVS
WHERE ENV_NAME='MYENVOPT'
/

Example SQL*Plus output:

ENV_OWNER            ENV_NAME   LANGUAGE_OPTIONS
-------------------- ---------- ----------------------
JSDEV01              MYENVOPT   js.strict=true

USER_MLE_ENV_IMPORTS

The [USER | ALL | DBA | CDB]_MLE_ENV_IMPORTS family of views lists imported modules.

MLE environments are the key enablers for resolving names of imported modules. Example 3-17 demonstrates a query against USER_MLE_ENV_IMPORTS to list IMPORT_NAME, MODULE_OWNER, and MODULE_NAME.

For more information about *_MLE_ENV_IMPORTS, see Oracle AI Database Reference

Example 3-17 List Module Import Information Using USER_MLE_ENV_IMPORTS

SELECT IMPORT_NAME, MODULE_OWNER, MODULE_NAME
    FROM USER_MLE_ENV_IMPORTS
    WHERE ENV_NAME='MYFACTORIALENV';
/

SQL*Plus output:

IMPORT_NAME            MODULE_OWNER              MODULE_NAME
---------------------- ------------------------- ------------------
FACTORIAL_MOD          DEVELOPER1                FACTORIAL_MOD