1. A bug in the way relation literals were parsed allowed the following...
Code: Select all
RELATION {x INTEGER, y INTEGER} {
TUPLE {x 1, z 1}
}
Code: Select all
RELATION {x INTEGER, y INTEGER}
TUPLE {x 1, y 1}
}
2. Due to a change in the way the third-party storage engine (Oracle Berkeley Java DB) generated exceptions -- introduced in Java DB version 4.0.71 -- Rel did not correctly handle an exception related to transactions and could wind up throwing its own internal exceptions. This was especially likely when attempting to drop a constraint or relvar immediately after a Rel error message had been generated. This has been corrected.
For more information, or to download Rel, see http://dbappbuilder.sourceforge.net/Rel.html