Home > Release Notes

4.1.2

Release Date  : April 30, 2007

Navigation through selection nodes (preview version)

An element declaration may define a XPath selection. In this case Manager User Interface provides a link so that the user can navigate to another table that may be filtered.

Common usage includes navigation through association links.

If the selection depends on the local occurrence state, the XPath expression must include a local path expresssion that put in "${...}". Please be cautious in this version on the spaces: one space before "=", no space after.

Example (this example is integrated in Tutorial):

<xs:element name="linkToAuthorTitles" minOccurs="0 maxOccurs="0" >
        <xs:annotation>
          <xs:appinfo>
            <mdm:select>
              <xpath>/root/Titles[au_id =${../au_id}]</xpath>
            </mdm:select>
          </xs:appinfo>
        </xs:annotation>
</xs:element>

 

Internal relational tables have been renamed

Bug 01432 has required to rename relational tables to shorter names and to change the prefixing policy. Please see ddl.sql files for more information.

However repositories created from version 4.0 up to version 4.1.1 remain supported.

Bug fixes:

  • [01424] Adaptation.checkActivable() does not check upon uptodate compiler.
  • [01425] Field selection in view mention path but not label. It is not consistant with node labeling in tables or nodes trees
  • [01426] View field selection: "equals" (or "=") criteria has a bug in resetting current value when changing field target (i.e. field type).
  • [01430] An inherited occurrence can be deleted in a child adaptation, it is then also deleted in the parent adaptation. Note: The manager does not allow to delete an inherited occurrence but only to occult it.
  • [01431] View documentation update is not effective.
  • [01432] Some relational databases do not support table names that have more than 18 characters. Some repository tables are longer than this limit.

Known limitations:

  • Performance: for large number of tables (in the order of 10,000 tables) and for large number of occurrences (in the order of 10,000,000 occurrences), optimizations are not yet available.
  • Merge process: in case of instances' add-add conflict, tables in the source are ignored.
    Workaround: first create instances and merge, then tables may be populated and merged.
  • Comparison and Merge: Header informations are not yet included in the comparison user interface nor in the merge process.
    Workaround: for merging header informations, a least one value must be updated on instance.
  • Repository locking: it is not yet detected when two Java virtual machines share the same physical repository.
    Workaround: Repositories' administrator must take care that a repository is not refered by two environments.
  • Access right management: a node can be set as ReadWrite even if it is not adaptable according to schema definition.

 

Home > Release Notes