db backend: t.addType(type) creates the t is-a type relation AND a t is-a t relation - Githubissues

tmlab / majortom

The MaJorToM ( Merging Topic Maps Engine ) project was founded to develop a lightweight, merging and flexible Topic Maps engine satisfying different business use cases. The engine provides a couple of new features above to other engines based on the Topic Maps API version 2.0.

1 stars 1 forks source link

db backend: t.addType(type) creates the t is-a type relation AND a t is-a t relation #42

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

janeDoe.addType(person) creates the person is-a person relation, as if
person.addType(person) is called.

Original issue reported on code.google.com by schulze....@googlemail.com on 25 Aug 2010 at 5:39

GoogleCodeExporter commented 9 years ago

Original comment by schulze....@googlemail.com on 25 Aug 2010 at 5:46

Changed title: db backend: t.addType() creates a t is-a t relation

GoogleCodeExporter commented 9 years ago

Original comment by schulze....@googlemail.com on 25 Aug 2010 at 5:58

Changed title: db backend: t.addType(type) creates the t is-a type relation AND a t is-a t relation

GoogleCodeExporter commented 9 years ago

t1.addType(t2) ist ok.

The problem is: type.getTypes()

t2.getTypes() gets all TII associations in which t2 plays a role. Then it 
happily returns the player of the type-role without checking that t2 plays the 
instance-role. 

I fix this.

Original comment by schulze....@googlemail.com on 25 Aug 2010 at 7:33

GoogleCodeExporter commented 9 years ago

Original comment by h.niederhausen@googlemail.com on 26 Aug 2010 at 9:16

Changed state: Fixed