16 Mnemosyne - Release Notes

This document describes the changes made to the Mnemosyne application. The intention of this document is to list all incompatibilities as well as all the enhancements, bugs and adjustments that have been noted for each previous release of Mnemosyne. Each release thus constitutes one section in this document. The title of each section is the Mnemosyne version number.

16.1 Mnemosyne 1.0.1

This release is a minor release and the release notes describes the difference between version 1.0.1 and version 1.0 of Mnemosyne.

16.1.1 Improvements and new features

• The documentation has been enhanced.
  

16.1.2 Fixed Bugs and malfunctions

No serious ones.

16.1.3 Incompatibilities

None.

16.1.4 Known bugs and problems

No new ones. See earlier release notes.

16.2 Mnemosyne 1.0

This is the first release of Mnemosyne as an own application, separate from the Mnesia DBMS Engine. The Mnemosyne application must be used in conjunction with Mnesia 3.0 or later.

16.2.1 Improvements and new features

N.A.

16.2.2 Fixed Bugs and malfunctions

N.A.

16.2.3 Incompatibilities

Mnemosyne has been separated from the Mnesia application and this has some minor implications:

• The compiler directive:
  

  -include_lib("mnesia/include/mnemosyne.hrl").

  that was mandatory in all Erlang modules containing embedded Mnemosyne queries has been replaced with:
  

  -include_lib("mnemosyne/include/mnemosyne.hrl").

  During the interim period, both compiler directives will be supported. However, in a future release the backward compatibility directive will be removed from Mnesia.
  
• The Mnemosyne application must be started before any query evaluation may be performed. Earlier, when Mnemosyne was a part of the Mnesia application, Mnemosyne was automatically started as an embedded part of Mnesia, this is not the case anymore. Now Mnemosyne must be started with application:start(mnemosyne), when Mnesia is started.
  However, a temporary configuration parameter embedded_mnemosyne has been added to Mnesia in order to make it possible to access the automatic start of Mnemosyne. By default embedded_mnemosyne is set to false, but if it is set to true Mnesia will start Mnemosyne as a supervised part of the Mnesia application as it did in previous releases.
  

16.2.4 Known bugs and problems

• The evaluation of Mnemosyne queries has undefined behavior if they are used in conjunction with nested transactions.
  
• The evaluation of Mnemosyne queries has an undefined behavior if the involved tables are updated after the cursor has been initiated.
  
• Mnemosyne queries should not be used on disc-only tables since the optimizer can't handle such tables.