18 Mnesia Session Release Notes
This document describes the changes made to the Mnesia Session application. The intention of this document is to list all incompatibilities as well as all enhancements and bug-fixes for each and every release of Mnesia Session. Each release of Mnesia Session constitutes one section in this document. The title of each section is the version number of Mnesia Session.
18.1 Mnesia Session 1.0
This release is a minor release and the release notes describes the difference between version 1.0 and version 0.81 of Mnesia Session.
18.1.1 Improvements and new features
- The documentation has been enhanced.
- The interface has been reworked internally to comply to Mnesia 3.4, more specifically, the record and table name relation has changed, see incompatibilities below.
18.1.2 Fixed Bugs and malfunctions
18.1.3 Incompatibilities
dirty_write, dirty_delete_object, dirty_match_object
functions have a new in parameter (Table Name). The table name parameter is needed in Mnesia Session to be able to differentiate between the table names and record names.
18.1.4 Known bugs and problems
No new bugs or problems. See earlier release notes.
18.2 Mnesia Session 0.81
This release is a minor release and the release notes describes the difference between version 0.81 and version 0.80 of Mnesia Session.
18.2.1 Improvements and new features
18.2.2 Fixed Bugs and malfunctions
- Two modules were missing in
mnesia_session.app
18.2.3 Incompatibilities
18.2.4 Known bugs and problems
- The documentation is not ready.
- The interface to
Mnesia Session
may be an object for change in future releases.
18.3 Mnesia Session 0.8
Mnesia
is written in Erlang and intended to be used with Erlang applications.
Mnesia Session
is a new application which enables access to the Mnesia DBMS from foreign programming languages (i.e. other languages than Erlang). TheMnesia Session
interface is defined inIDL
(an Interface Definition Language standardized byOMG
(the Object Management Group)).18.3.1 Improvements and new features
Mnesia Session
contains two back-ends. One for access via the standardizedIIOP
protocol and the other for access via Erlang's proprietary distribution protocol.
Following is a brief summary of the available configuration parameters:
- debug ::= none | verbose | debug | trace
- enable_corba ::= false | true
- corba_connector_name ::= A valid COSS name
18.3.2 Fixed Bugs and malfunctions
18.3.3 Incompatibilities
18.3.4 Known bugs and problems
- The documentation is not ready.
- The interface to
Mnesia Session
may be an object for change in future releases.
Any comments regarding the Mnesia Session application would be appreciated.