Mnesia
is written in Erlang and intended to be
used for Erlang applications.
The Mnesia Session
application enables access
to the Mnesia DBMS from foreign programming languages
(i.e. other languages than Erlang). The Mnesia Session
interface is defined in IDL
(an Interface Definition
Language standardized by OMG
(the Object Management
Group)).
This module is automatically generated from the IDL
specification mnesia_session.idl
and is documented in the IDL specification.
Mnesia Session reads the following application configuration parameters:
-mnesia_session corba_connector_name Name
. This
parameter controls which initial name Mnesia Corba
Connector is bound. This parameter is only used when the
enable_corba
is set to true. The name is validated
by using lname:check_name(Name)
.
See the Orber
application for details. The default
name is {'CosNaming_NameComponent',
"IDL:CosNaming/NameComponent:1.0", "mnesia_corba_connector",
[]}
.-mnesia_session debug Level
Controls the debug level of Mnesia Session.
Possible values are:
none
verbose
debug
trace
-mnesia_session enable_corba true | false
. This
flag enables Mnesia Session to
access Mnesia via CORBA. If CORBA access is enabled, the
application Orber must be started in order to start Mnesia
Session. The default is false
.
First the SASL application parameters are checked, then the command line flags are checked, and finally, the default value is chosen.
mnesia(3), orber(3), application(3)