NAME

       UR::Env - Environment variables that control UR behavior

DESCRIPTION

       UR uses several environment variables to change its behavior or provide additional debugging information.

       UR_STACK_DUMP_ON_DIE <bool>
           When  true,  has  the  effect of turning any die() into a Carp::confess, meaning a stack dump will be
           printed after the die message.

       UR_STACK_DUMP_ON_WARN <bool>
           When true, has the effect of turning any warn() into a Carp::cluck, meaning  a  stack  dump  will  be
           printed after the warn message.

       UR_CONTEXT_ROOT <string>
           The  name  of  the  Root  context  to  instantiate  when  the  program  initializes.   The default is
           UR::Context::DefaultRoot.  Other Root Contexts can be used, for  example,  to  connect  to  alternate
           databases when running in test mode.

       UR_CONTEXT_BASE <string>
           This  value  only changes in a sub-process which goes to its parent process for object I/O instead of
           the root (which is the default value for the base context in an application).

       UR_CONTEXT_CACHE_SIZE_HIGHWATER <integer>
           Set   the   object   count   highwater   mark   for   the   object   cache    pruner.     See    also
           "object_cache_size_highwater" in UR::Context

       UR_CONTEXT_CACHE_SIZE_LOWWATER <integer>
           Set    the    object    count    lowwater   mark   for   the   object   cache   pruner.    See   also
           "object_cache_size_lowwater" in UR::Context

       UR_DEBUG_OBJECT_RELEASE <bool>
           When true, messages will be printed to STDERR whenever objects are removed  from  the  object  cache,
           such  as when the object pruner marks them for removal, when they are garbage collected, unloaded, or
           deleted.

       UR_DEBUG_OBJECT_RELEASE <bool>
           When true, messages will be printed to STDERR whenever the object pruner finishes its work, and  show
           how many objects of each class were marked for removal.

       UR_CONTEXT_MONITOR_QUERY <integer>
           When  true  (non-zero), messages will be printed as the Context satisfies queries, such as when get()
           is called on a class, or while processing an iterator created through SomeClass->create_iterator  and
           iterator->next().  If the value is 1, then only queries about Non-UR classes are printed.  If 2, then
           all queries' information is printed.

       UR_DBI_MONITOR_SQL <bool>
           If  this  is true, most interactions with data sources such as connecting, disconnecting and querying
           will print messages to STDERR.  Same as "UR::DBI->monitor_sql()".  Note  that  this  affects  non-DBI
           data sources as well, such as file-based data sources, which will render file I/O information instead
           of SQL.

       UR_DBI_SUMMARIZE_SQL <bool>
           If  true, a report will be printed to STDERR as the program finishes about what SQL queries have been
           done during the program's execution, and how many times they were executed.  This is  helpful  during
           optimization.

       UR_DBI_MONITOR_EVERY_FETCH <bool>
           Used  in conjunction with UR_DBI_MONITOR_SQL, tells the data sources to also print messages to STDERR
           for each row fetched from the underlying data source. Same as "UR::DBI->monitor_every_fetch()".

       UR_DBI_DUMP_STACK_ON_CONNECT <bool>
           Print  a  message  to  STDERR  only  when  connecting  to  an  underlying  data  source.    Same   as
           "UR::DBI->dump_stack_on_connect()"

       UR_DBI_EXPLAIN_SQL_MATCH <string>
           If the query to a data source matches the given string (interpreted as a regex), then it will attempt
           to   do   an   "explain   plan"   and   print  the  results  before  executing  the  query.  Same  as
           "UR::DBI->explain_sql_match()"

       UR_DBI_EXPLAIN_SQL_SLOW <float>
           If the time between a prepare and the first fetch of a query is  longer  than  the  given  number  of
           seconds,    then   it   will   do   an   "explain   plan"   and   print   the   results.    Same   as
           "UR::DBI->explain_sql_slow()"

       UR_DBI_EXPLAIN_SQL_CALLSTACK <bool>
           Used in conjunction with UR_DBI_EXPLAIN_SQL_MATCH and UR_DBI_EXPLAIN_SQL_SLOW, prints a  stack  trace
           with Carp::longmess.  Same as "UR::DBI->explain_sql_callstack()"

       UR_DBI_MONITOR_DML <bool>
           Like  UR_DBI_MONITOR_SQL,  but  only prints information during data-altering statements, like INSERT,
           UPDATE or DELETE.  Same as "UR::DBI->monitor_dml()"

       UR_DBI_NO_COMMIT <bool>
           If true, data source commits will be ignored.  Note that saving still occurs.   If  you  are  working
           with  a  RDBMS  database,  this means During UR::Context->commit(), the insert, update and delete SQL
           statements will be issued, but the changes will not be  committed.   Useful  for  testing.   Same  as
           "UR::DBI->no_commit()"

       UR_USE_DUMMY_AUTOGENERATED_IDS <bool>
           If  true,  objects  created  without ID params will use a special algorithm to generate IDs.  Objects
           with these special IDs will never be saved to  a  data  source.   Useful  during  testing.   Same  as
           "UR::DataSource->use_dummy_autogenerated_ids"

       UR_USED_LIBS
           If true, prints a message to STDERR with the contents of @INC just before the program exits.

       UR_USED_MODS
           If  true,  prints a message to STDERR with the keys of %INC just before the program exits.  This will
           be a list of what modules had been loaded during the life of the program.  If UR_USED_MODS is greater
           than 1, then it will show the key/value pairs of %INC, which will  show  the  path  each  module  was
           loaded from.

perl v5.38.2                                       2024-06-15                                       UR::Env(3pm)