#1091 closed defect (fixed)

New annotation types in multiple new release version

Reported by: Nicklas Nordborg Owned by:
Priority: critical Milestone: Relax v1.4
Component: net.sf.basedb.relax Keywords:
Cc:

Description

When a new annotation type is introduced in a release the importer will only set a value on existing item the first time (eg. when the annotation type is new).

This will not work as expected if a release is actually multiple releases with a new major release with new items as well as updates to older releases. For example, the next major release will be 5.0 and it may also include updates to 4.1, 3.2 and 2.5.

If this set of releases introduces new annotations (it will!) then, depending on the import order, the new annotations may not be set on all existing items. For example if we start with the 2.5 import only items in the 2.x releases will get the new annotations. Since the annotation type is not considered "new" when importing for 3.2 or 4.1, existing items will not get a value.

This should be changed so that if an existing item doesn't have a value it will be set.

Change History (1)

comment:1 Changed 23 months ago by Nicklas Nordborg

Resolution: fixed
Status: newclosed

(In [5181]) Fixes #1091: New annotation types in multiple new release version

The annotations should now be created if there is no existing value.

Note: See TracTickets for help on using tickets.